Connect Claude

Nexus MCP works as a remote custom connector in Claude.ai, Claude Desktop, Cowork, and supported mobile clients. The connection uses Nexus OAuth; no API key is pasted into Claude.

Anthropic's current availability, organization controls, and setup flow are documented in the official remote custom connector guide.

Before you start

• The customer mcp. hostname must be publicly reachable with valid TLS.
• Use the member /mcp endpoint shown below.
• The user needs a valid Nexus UI account and permissions in that tenant.
• Team/Enterprise users may need an Owner to add the connector first.

Remote connector traffic originates from Anthropic's cloud, even when Claude Desktop is used. A VPN-only or LAN-only server will not work as a remote connector.

Endpoint

https://mcp.example.com/mcp

Individual account setup

1. Open Customize → Connectors.
2. Select + → Add custom connector.
3. Enter Nexus Member as the name.
4. Enter https://mcp.example.com/mcp as the complete MCP URL.
5. Leave manual OAuth client credentials empty; Nexus supports dynamic public-client registration.
6. Select Add, then Connect.
7. Sign in through the normal Nexus frontend if required.
8. Review the tenant, callback origin, and scopes, then approve.

Team or Enterprise setup

An Owner or Primary Owner first:

1. opens Organization settings → Connectors;
2. selects Add → Custom → Web;
3. enters the Nexus MCP URL;
4. leaves optional client ID/secret fields empty for dynamic registration;
5. adds the connector.

Each user then opens Customize → Connectors, finds Nexus, selects Connect, completes Nexus authorization, and enables the connector for a conversation.

First test

Use Nexus to show my identity type, tenant, enabled modules, OAuth scopes, and visible capability groups. Do not change anything.

Then try a role-appropriate request:

List my active advertiser campaigns, sorted by daily spend. Return CID, name, bid, budgets, spend, status, pagination completeness, and exact counts.

or:

Analyze Search statistics for the last seven complete days and the previous equal period. Recompute weighted KPIs and identify anomalies using only Nexus evidence.

Testing a safe change

Prepare pausing campaign 12345. Read current state, validate the operation contract, and show the exact non-secret diff. Do not execute until I explicitly confirm.

Claude should pause before execution. After confirmation it should use the payload-bound approval and idempotency key, then verify the new state.

Common problems

Symptom	Resolution
Connector cannot reach Nexus	Verify public DNS, TLS chain, firewall, and the exact MCP URL
Authorization opens the wrong account	Sign out of Nexus, select the intended member, and reconnect /mcp
OAuth loops or callback fails	Remove/reconnect, clear stale sessions, and verify the callback origin policy
Tool missing	Check nexus_whoami, role, module, and OAuth scopes
Change blocked	Confirm nexus:write and complete the exact preview/confirmation workflow
Reauthorization requested	The session expired, was revoked, or Nexus identity/tenant changed

Continue with Available MCP tools for examples or MCP troubleshooting for server diagnostics.