MCP

Supported protocol versions are 2025-06-18, 2025-03-26 and 2024-11-05.

OAuth 2.1 is the default. A client that supports it discovers Nextora’s authorization server from the WWW-Authenticate header of a 401 and from /.well-known/oauth-protected-resource, registers itself, and opens the Nextora sign-in in your browser. You approve the access; the client never sees your password.

An API key works too, for clients without OAuth or for unattended setups: send it as Authorization: Bearer sk_live_…, exactly as for the REST API.

Tools act as the signed-in user — or the key’s owner — with their role and record visibility. Scopes then decide which tools a connection sees: a read-only scope set shows no tools that change data.

An OAuth connection asks for read and write access to CRM records, custom entities, communications, analytics and automation, plus creation:write for the AI workshops. Nextora grants only what the user’s role may hold: admin is never granted to someone who is not a workspace admin. An API key carries the scopes chosen when it was created.

Changes made through MCP run the same automations and send the same webhooks as changes in the app.

In Claude, open Settings → Connectors and add a custom connector with the URL https://mcp.nextora.co/mcp — or your workspace’s https://acme.nextora.co/api/mcp. Claude opens the Nextora sign-in; approve, and the tools appear in your chats. On team plans an owner may need to add the connector first.

Add the server, then run /mcp inside Claude Code and choose nextora to sign in:

claude mcp add --transport http nextora https://acme.nextora.co/api/mcp

Or authenticate with an API key instead of OAuth:

claude mcp add --transport http nextora https://acme.nextora.co/api/mcp \
  --header "Authorization: Bearer $NEXTORA_API_KEY"

To share the server with a project, commit an .mcp.json; each person provides their own key through the environment:

{
  "mcpServers": {
    "nextora": {
      "type": "http",
      "url": "https://acme.nextora.co/api/mcp",
      "headers": { "Authorization": "Bearer ${NEXTORA_API_KEY}" }
    }
  }
}

ChatGPT adds remote MCP servers as custom connectors; depending on your plan this may require developer mode or an admin to enable it. Create a connector with the URL https://mcp.nextora.co/mcp, choose OAuth for authentication, and sign in to Nextora when ChatGPT asks.

Add Nextora to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project. Cursor connects and asks you to sign in to Nextora:

{
  "mcpServers": {
    "nextora": {
      "url": "https://acme.nextora.co/api/mcp"
    }
  }
}

To use an API key instead, add "headers": { "Authorization": "Bearer sk_live_…" } next to url, and keep that file out of version control.

Any client that supports remote servers over Streamable HTTP works: give it the URL and let it sign in with OAuth, or configure a bearer token. Clients that only run local servers over stdio need a bridge that forwards to the remote URL.

Tools are grouped by domain. /api/mcp serves them all, and /api/mcp/{category} serves one group:

Settings → Developers → MCP connections shows the apps connected to your workspace. A connection that uses an API key ends when you revoke the key.