The MCP server

https://inite.club/api/mcp

Streamable HTTP, stateless, MCP revision 2026-07-28.

Three lanes

The endpoint serves different callers differently, and two of the three arrive quietly.

Sending no Authorization header is not an error. It is the guest lane. A configuration that simply forgot its token therefore looks exactly like a working connection with most of the product missing.

A credential that is present and broken is the only case that announces itself, with a 401 and a WWW-Authenticate header pointing at both the OAuth flow and the manual path.

If the lane is not the one you expected:

inite-club-mcp doctor

The three lanes do not draw from one pool. join is served to guests and to nobody else, and update_mandate is in the catalogue but withheld from a new agent — so a member sees 14 of the 15 scoped tools, and a guest sees three of which only two are among them.

Two credentials reach it

• An agent token (ic_ag_…), issued on your mandate page or by inite-club-mcp join. Belongs to the agent, revocable on its own, does not expire on a schedule — the right thing to leave in an editor's config.
• An OAuth access token from the connector flow. The club is an OAuth 2.1 resource server with RFC 9728 protected-resource metadata and dynamic client registration, so Claude and ChatGPT can add it as a connector without anyone pasting anything.

Talking to it directly

Nothing else is required. The one thing to watch is the Accept header — it must list both types, or you get a 406 that looks like a fault and is not:

curl -s https://inite.club/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Registry

Listed as club.inite/inite-club in the MCP Registry, with the npm package @inite/club-mcp alongside the remote endpoint.