Cursor & custom MCP clients

Anything that speaks Model Context Protocol revision 2025-03-26 over Streamable HTTP can connect, including Cursor, in-house agents and your own scripts. OAuth is auto-discovered; for clients that only handle static tokens, a bearer key works.

Endpoints

OAuth clients

Point the client at the server URL and let it read the discovery document. Dynamic client registration is supported at the registration endpoint, so there is no application to create by hand and no client secret to distribute. PKCE with S256 is required.

Static-token clients

Generate a key in the console under Settings → API Keys, choose Custom, and copy the msh_cus_… value. It is displayed once. Send it as a normal bearer token on every request.

{
  "mcpServers": {
    "msharti": {
      "transport": "http",
      "url": "https://mcp.msharti.dev/mcp",
      "headers": {
        "Authorization": "Bearer msh_cus_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Cursor

1. Open MCP settings. Cursor exposes MCP servers in its settings panel under Model Context Protocol.
2. Add an HTTP server. Use https://mcp.msharti.dev/mcp as the URL. Where Cursor supports OAuth, let it discover the flow; otherwise supply the bearer header above.
3. Confirm tool discovery. Msharti's tools should appear in the tool list. If the list is empty, your role's allowlist is empty or no connectors are configured yet.

Building your own agent against the endpoint

This endpoint is also how in-house agents connect. The pattern is the same as for any assistant: give the agent its own API key, bind that key to a role whose allowlist contains exactly the tools the agent needs, and read the audit log by key prefix to see what it did. That whole process is written up in build an agent.

Behaviour worth knowing