Configuring MCP clients
Any client that speaks MCP over HTTP can use this server. You always need the same base URL (below) for every connection,
the Authorization: Bearer header with a PAT, and headers your client expects for JSON/SSE (often Accept: application/json, text/event-stream).
Scope is in the token, not in the URL—IDEs may list several “MCP servers” in their UI, but they can all point here with different PATs.
https://mcp.richbot9000.com/mcp
Getting a token
Log in to this site and open MCP tokens
(if your account has permission to mint tokens). Choose a tool group, mint a PAT, and copy it once.
Each PAT is scoped to that group via Sanctum ability mcp:tool-group:{id}.
Cursor
In Cursor, add an MCP server entry that points at this URL and configure HTTP headers for the Bearer token.
Use the official Cursor docs for “MCP” / remote servers—field names change between versions, but the idea is:
base URL = https://mcp.richbot9000.com/mcp, plus authentication header with your PAT.
MCP Inspector
The MCP Inspector
is useful for debugging initialize, tools/list, and tools/call.
Point it at the same URL and supply the Bearer token when prompted for HTTP auth.
Other services & servers
Another Laravel app, a worker, or a CI job can call this endpoint the same way: HTTPS POST, JSON-RPC body, Bearer PAT. You can mint many tokens per user account; each PAT selects one tool group. Different groups require different PATs—there is no “all groups” token in v1.