This is Claude's remote custom connector, added from Claude's own settings. If what you run is the claude command in your terminal, you want Connect Claude Code instead — a different client, with a different setup.
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 as your client. The page then shows the endpoint URL of this server, ready to copy.
Add the connector
Open Customize → Connectors → Add custom connector and add the endpoint URL the MCP page shows.
Then configure the connector to send your token on every call:
Authorization: Bearer <your-token>
If your version of the connector does not allow custom headers, you will need a proxy in front of it that adds the Authorization header.
The endpoint has to be public HTTPS
Claude's remote connectors run from Anthropic's infrastructure, not from your machine. The endpoint must be reachable from the internet over HTTPS. localhost will not work, with or without HTTPS. Every other client on the MCP page runs beside your code, so this restriction is this one's alone.
Use the https URL, never http. On plain http the server redirects, and clients drop both the Authorization header and the request body on that redirect — so the connection fails exactly as if the token were wrong.
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
Ask Claude to run list_rules. It should come back with the configured rules, which confirms both that the token works and that the analyzer is set up.
You can also test the token from your terminal before touching the connector at all. 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 | the endpoint is the http URL, and the redirect strips the header |
use the https URL |
| Nothing connects at all | the endpoint is localhost or is not reachable from the internet |
publish it over HTTPS |
| Claude says a tool does not exist | the server is connected but restricted to a subset of tools | remove the tool allowlist, then ask Claude to list the tools it can see |
Next
Install the toolkit — the connector has no disk of yours to write to, so the agents and commands are installed from Claude Code, Codex or DeepSeek Harness, where your files are.