Connect Claude Code

Claude Code supports remote HTTP MCP servers and OAuth authentication. Add the Nexus URL first, then authorize it interactively.

Step 1: use the member endpoint

https://mcp.example.com/mcp

Step 2: add Nexus

claude mcp add --transport http nexus https://mcp.example.com/mcp

Use --scope user if the private connection should be available in all your local projects. Avoid a shared project configuration for customer-specific production access unless your team has explicitly reviewed it.

Step 3: authorize with OAuth

1. Start Claude Code with claude.
2. Enter /mcp.
3. Select nexus.
4. Choose the authentication/connect action.
5. Follow the browser link.
6. Sign in through the normal Nexus frontend if needed.
7. Review the tenant, callback origin, and OAuth scopes.
8. Approve and return to Claude Code.

Claude Code stores the OAuth credential and refreshes it automatically. Use Clear authentication from /mcp to revoke the local connection.

Step 4: verify

claude mcp list
claude mcp get nexus

In the Claude Code session, ask:

Use Nexus nexus_whoami and show my tenant, identity type, modules, OAuth scopes, and visible tool groups. Do not change anything.

Concrete tests

Campaign list

List all paused campaigns I own. Follow nextOffset until it is null and report whether source pagination and counts are complete.

Full campaign configuration

Get campaign 12345 and summarize budget, schedule, geo, device, browser, carrier, frequency cap, and allow/block lists. Do not change it.

Statistics

Analyze advertiser statistics from 2026-08-01 to 2026-08-17 and compare the previous equal-length period. Show complete totals, weighted KPIs, rankings, anomalies, and data-quality issues.

Prepared write

Prepare changing campaign 12345's daily budget to 200 EUR. Show the exact validated diff and wait for explicit confirmation before any write.

Optional trusted direct-JWT mode

Only when the MCP deployment explicitly enables ALLOW_DIRECT_JWT=true, trusted automation may configure the current Nexus UI access JWT as a Bearer header:

claude mcp add --transport http nexus-direct https://mcp.example.com/mcp \
  --header "Authorization: Bearer $NEXUS_ACCESS_JWT"

This is not required for normal Claude Code use, is not a UUID integration API key, and delegates refresh/rotation responsibility to the client. Prefer OAuth for interactive connections.

Security notes

• Never put tokens in prompts, URLs, screenshots, repositories, or support messages.
• Confirm that the OAuth page shows the expected customer tenant and callback origin.
• Request only the scopes required for the workflow.
• Review every mutation preview; approval is bound to the exact payload.
• Clear authentication and revoke the Nexus MCP session when a device is lost or access is no longer needed.

Continue with Available MCP tools.