Client Setup

Claude

Trove is one connection in Claude, added via Claude’s Add custom connector dialog. Add it once from claude.ai on the web or the Claude desktop app — the Claude mobile apps can’t add it, but once added, Trove works there too.

1. On claude.ai (web) or the Claude desktop app, open Settings → Connectors and click Add custom connector.
2. Set Name to Trove and Remote MCP server URL to https://api.ontrove.sh/mcp. Leave Advanced settings collapsed — Trove registers your client automatically, so no OAuth Client ID or Secret is needed.
3. Click Add. Claude opens a browser window to sign in to Trove (create your account if you haven’t) and authorize the connection.

OAuth is handled automatically — Claude discovers the authorization server via .well-known/oauth-protected-resource and registers itself dynamically. No config file to edit, no restart.

To verify, ask Claude:

“What tools does Trove give you?”

After you deploy a toolkit, open the connector’s ⋮ menu → Refresh tools list to pull in its tools. See the quickstart for the full walkthrough.

Claude Code

Add Trove as a remote MCP server from your terminal:

claude mcp add --transport http trove https://api.ontrove.sh/mcp

This registers Trove globally so it’s available in every project. OAuth is handled automatically — a browser window opens for you to sign in on first use.

To verify, start a conversation and ask:

“List my Trove sources”

Scoped to a project

To add Trove only for a specific project, run the command from that project’s directory with the --scope project flag:

claude mcp add --transport http --scope project trove https://api.ontrove.sh/mcp

Cursor

1. Open Cursor Settings (Cmd+, on macOS)
2. Navigate to MCP Servers
3. Add a new server with:
   • Name: trove
   • Type: streamable-http
   • URL: https://api.ontrove.sh/mcp

Authentication works the same way as Claude Desktop. Cursor will open a browser for OAuth when you first connect.

Other MCP Clients

Any client that implements the MCP specification can connect to Trove.

Setting	Value
URL	https://api.ontrove.sh/mcp
Transport	Streamable HTTP (POST)
Auth	Bearer token in Authorization header
Protocol	JSON-RPC 2.0

Session management

After sending an initialize request, the server returns an MCP-Session-Id header. Store this value and include it as a header in all subsequent requests. See Transports for the full handshake sequence.

Getting a token

If your client does not support OAuth discovery, obtain a bearer token from Clerk directly and pass it in the Authorization: Bearer <token> header.