Server Map
Shared Assumptions
- If bearer auth is disabled, clients can connect directly without auth.
- If bearer auth is enabled, use a client that supports custom
Authorization headers.
- Tool calls use the generated request envelope:
{"request": {...}}.
- Verify
/health before wiring the MCP URL into a production client.
- Direct streamable HTTP calls require a session handshake before
tools/list or tools/call.
- n8n can call the same endpoints either with an MCP Client node or with HTTP Request nodes. See n8n Workflows.
Cursor
Cursor reads MCP config from either project-local .cursor/mcp.json or global ~/.cursor/mcp.json.
If a server is authless, omit the headers block for that entry.
Claude Desktop
Claude Desktop uses remote connectors for remote MCP servers.
- Open Settings > Connectors.
- Choose Add custom connector.
- Enter a connector name and the remote MCP URL.
- Connect and enable the tools you want.
Claude remote connectors support authless and OAuth-based remote MCP servers. They are not a good fit for static bearer-header-only auth configured manually in local JSON. For protected endpoints, use an OAuth-capable gateway, a trusted network path, or an authless connector-facing endpoint with a limited tool surface and rate limiting.
Generic HTTP / Streamable MCP Clients
Health Check
Python FastMCP Client
Verification Checklist
/health responds successfully.
tools/list returns the expected server-specific tools.
- Auth behavior matches the selected client.
- One small deterministic tool call succeeds before the server is used in a longer workflow.