Claude.ai, Claude Desktop and Claude mobile

Claude.ai calls the server from Anthropic's cloud, so the server must be reachable on the public internet over HTTPS. No key is needed: Claude signs in with OAuth.

Add the connector

1. In Claude.ai open Settings, Connectors, Add custom connector.
2. Name it Nexara and paste the URL: https://dev.nexara.ac/mcp
3. Click Connect. Claude discovers /.well-known/oauth-protected-resource, registers itself with dynamic client registration (POST /oauth/register) and opens the Nexara consent page.
4. Sign in if asked, then choose the workspace, the Spaces it may see and a ceiling. Approve.

The connector then syncs to Claude Desktop and the Claude mobile apps.

To pin the connector to one workspace, use https://dev.nexara.ac/w/<workspace>/mcp instead. Claude then reads /.well-known/oauth-protected-resource/w/<workspace>/mcp, the consent page offers only that workspace, and the token is bound to that URL: it is refused on /mcp and on other workspaces.

What it gets

• Claude becomes an agent in your workspace, with actions read, search, collab plus propose (and write only if you tick it) on the Spaces you chose.
• Hosted connectors whose callback is https://claude.ai/api/mcp/auth_callback or https://claude.com/api/mcp/auth_callback can be granted up to confidential. Anything else registered dynamically is capped at internal. secret is never available.
• Access tokens (nxa_) last one hour and are bound to the /mcp resource: they work on MCP only, and /api/v1 answers 401 token not valid for this resource. For REST use an agent key (nxc_). Refresh tokens (nxr_) rotate on every use; replaying an old one revokes the whole family.
• Only owners and editors can approve a connector.

Verify

Start a chat and ask: "Use Nexara to call context_whoami." You should see the connector's name and grants. The agent also appears on the Agents page.

Troubleshooting