Quickstart
First call.
Four steps. Everything runs under your identity — you will only ever see what the same person would see signed into Club OS.
Request a key
Keys are issued per company and scoped to the tools you need — there is no self-serve signup, because every key is bound to a real identity in the platform. Request one, naming what the agent should do and which scopes it needs.
Point a client at the endpoint
Streamable HTTP, JSON-RPC 2.0 over POST. Protocol revision 2026-07-28 is negotiated.
{
"mcpServers": {
"clubos": {
"type": "http",
"url": "https://mcp.thequantumclub.com/mcp",
"headers": { "Authorization": "Bearer tqc_mcp_..." }
}
}
}
Check what your key can see
tools/list is filtered to your
granted scopes. An empty list means you are not authenticated — an invalid or
revoked key is rejected outright, so an empty list never means "this server has no tools".
curl -sS -X POST https://mcp.thequantumclub.com/mcp \
-H "Authorization: Bearer $TQC_MCP_KEY" \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Make a call
Every result carries resultType,
and list results paginate with nextCursor.
Pass the cursor back to continue.
curl -sS -X POST https://mcp.thequantumclub.com/mcp \
-H "Authorization: Bearer $TQC_MCP_KEY" \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"search_jobs","arguments":{"limit":5}}}'
Next: the tool catalogue and the limits and error reference.