Connect Rail Cove to Claude Desktop

Follow the steps

1. 1

   Use a deployed Rail Cove MCP URL such as https://YOUR_DEPLOYED_API_ORIGIN/mcp. It must be reachable from the public internet over HTTPS.

2. 2

   In Claude Desktop, open Customize → Connectors, choose Add custom connector, and enter the exact Rail Cove MCP URL.

3. 3

   Complete the OAuth sign-in and approve only the Rail Cove scopes the conversation needs. Keep library:write out unless capture_note is intentional.

4. 4

   Enable the connector for the conversation, review the available tools, and revoke the connection from Claude's connector controls or Rail Cove Settings → Connections when finished.

Choose only the access you need

Personal keys always expire: the default is 90 days and the maximum is 365 days. Choose a non-empty subset of the available scopes and revoke the key when the connection is finished.

Code examples

Replace placeholders in your own protected environment. Never paste a real key into a public page, browser bundle, prompt, screenshot, issue or repository.

https://YOUR_DEPLOYED_API_ORIGIN/mcp

What to know

• Anthropic's remote connector flow calls the remote server from Anthropic's cloud infrastructure, including when the user is operating Claude Desktop. A private localhost, VPN-only, or firewalled API is not a valid remote connector target.
• The current server does not ship the local .mcpb/stdio path documented separately by Anthropic. Do not use a claude_desktop_config.json recipe for Rail Cove until a tested local extension exists.
• A personal bearer key is supported by the Rail Cove protocol, but the Claude Desktop custom-connector UI guide should lead with OAuth until a pasted-key path is verified for that client.

Troubleshooting

• If Claude cannot reach the server, check public HTTPS reachability, the exact /mcp path, and the reverse proxy's forwarded headers.
• If OAuth returns a resource or redirect error, restart from the connector flow and preserve the exact advertised resource URL and redirect values.
• If a write tool appears unexpectedly, disconnect and reconnect with a grant that omits library:write, or revoke the grant in Rail Cove Settings → Connections.
• If you need localhost access, wait for a separately shipped and tested local extension; the current remote connector path cannot reach a developer's localhost.