MCP on Claude Desktop

Claude Desktop supports MCP through local and remote transports. Onboard exposes hosted MCP at https://rest.onboard.io (see MCP setup for exact paths and authentication).

Recommended pattern (OAuth)

Anthropic’s remote MCP and custom connectors use per-user OAuth, not an org-wide shared API key. See connector authentication.

1. Confirm MCP setup requirements and that hosted MCP OAuth is enabled for your tenant.
2. An admin registers the connector: SSE URL https://rest.onboard.io/mcp/sse (no trailing slash), OAuth Client ID from Integrations → API, and allowed callbacks (for Claude web: https://claude.ai/api/mcp/auth_callback).
3. Each user completes sign-in in Claude Desktop or Claude.ai before tools run—access follows that user’s Onboard permissions, not a single shared key.

For field-by-field help, MCP Inspector testing, and production Client ID reference, see Connecting to Onboard MCP.

For API-key-first clients (Cursor, Quick, Raycast), see MCP desktop clients and Security & permissions (MCP).

Anthropic publishes MCP client behavior in their own help center; use their latest instructions if UI labels differ from the steps above.

Security

OAuth ties MCP to individual users—offboard people in Onboard and revoke their login, not only a shared integration key. Prefer company-managed machines and the Security checklist. Compare API key vs OAuth in Security & permissions (MCP).

Related

• Connecting to Onboard MCP — OAuth, Inspector, Client ID from Integrations
• MCP setup
• MCP desktop clients