Client Setup

Claude Desktop

1. Edit the config file

Open the Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Add Trove to the mcpServers section:

{
  "mcpServers": {
    "trove": {
      "type": "streamable-http",
      "url": "https://api.ontrove.sh/mcp"
    }
  }
}

2. Authenticate

OAuth is handled automatically. When Claude Desktop connects to Trove for the first time, it discovers the Clerk authorization server via .well-known/oauth-protected-resource and opens a browser window for you to sign in.

3. Restart Claude Desktop

Save the config file and restart Claude Desktop for the changes to take effect.

4. Verify

Ask Claude something like:

“List my Trove connectors”

If Trove is connected, Claude will call trove_list_connectors and show your configured data sources.

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 connectors”

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.