Connect Claude Code

Get your token first — see Get your access token. You need it in hand, because it is shown only once.

On the MCP page, pick Claude Code as your client. The page then shows the endpoint URL of this server, ready to copy.

Claude Code runs on your machine, so localhost works here: unlike Claude's remote connector, the endpoint does not have to be public or reachable from the internet.

Add the server

One command, from the project you want it in:

claude mcp add --transport http weblabor <the endpoint the MCP page shows> \
  --header "Authorization: Bearer <your-token>"

Where it gets written

claude mcp add writes the server to one of three places. Pass --scope to pick one:

Scope	Where it lands	Who gets it
`local`	`~/.claude.json`, under the current project's entry	you, in this project only — this is the default
`project`	`.mcp.json` at the repository root	everyone who checks the repository out
`user`	`~/.claude.json`, at the top level	you, in every project on this machine

A project scoped server lives in a file you commit, so the token must not be in it. ${VAR} is expanded inside headers, and that is what keeps it out:

{
  "mcpServers": {
    "weblabor": {
      "type": "http",
      "url": "<the endpoint the MCP page shows>",
      "headers": { "Authorization": "Bearer ${WEBLABOR_ANALYZER_TOKEN}" }
    }
  }
}

Each developer then exports their own token in the shell they launch Claude Code from:

export WEBLABOR_ANALYZER_TOKEN="<your-token>"

A project server has to be approved once

The first time you open a project whose .mcp.json declares a server, Claude Code asks whether you trust it. Until you say yes, the server is not used. And if you say no, the answer is remembered and nothing asks again: the tools are simply never there, with no error to go looking for.

claude mcp reset-project-choices clears that answer, so you are asked again.

A change needs a new session

The configuration is read when a session starts. Editing .mcp.json or running claude mcp add again while a session is open changes nothing until you open a new one.

Do not restrict the tools

Leave the server with all of its tools. Cutting it down to validate_code blocks install_toolkit, get_standard and get_guide, which are what make the rest of this work.

Check the connection

Run /mcp inside a session: it lists the servers and the state of each one. Then ask Claude Code for list_rules. It should come back with the configured rules, which confirms both that the token works and that the analyzer is set up.

To test the token before configuring anything, run this in your terminal. The response contains serverInfo:

curl -X POST <the endpoint the MCP page shows> \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

When it does not connect

What you see	Cause	Fix
Every call fails as if the token were wrong	a space came with the token when you pasted it, at either end	add the server again with the token trimmed
`/mcp` does not list the server at all	the configuration changed while the session was running	open a new session
The server is in `.mcp.json` but none of its tools are there	the project server was declined once, and the answer is remembered	run `claude mcp reset-project-choices`, open a session and accept
Claude Code says a tool does not exist	the server is restricted to a subset of tools	remove the restriction, then ask it to list the tools it can see

Install the toolkit — the agents and commands land under ~/.claude, written by Claude Code itself.