Getting a key
MCP keys are separate from your RESTX-API-Key (see Authentication) and carry their own scopes.
- Open Integrations from your profile menu.
- Go to MCP Server.
- Create a key and pick the scopes it needs — least privilege by default. A read-only key can be handed to an agent you don’t fully trust yet.
Connecting a client
Server URL:https://mcp.getnexor.ai/mcp
Claude Code
~/.cursor/mcp.json or Claude’s connector settings)
~/.codex/config.toml)
Scopes
A key can only call tools within its granted scopes.Tool catalog
Workflows (agents)
This is the full “create an agent that does A, then B, then C” toolset — it maps directly to the Workflows and Workflow Tools REST endpoints.Custom tools
Tools scoped to a single agent, with no catalog inheritance. Prefer the client tools catalog below when a tool should be reusable across agents.Client tools catalog
A two-level model: a client tool is a reusable definition in the client’s catalog; assigning it to an agent creates an inherited copy that stays in sync with the catalog tool on future edits. It maps to the Client Tools REST endpoints.Background jobs
Leads
Rules
People
Messaging
Account
Reports
Phone numbers
Internal-admin keys additionally have
release_phone_number, transfer_number, and dialing-permission tools.
WhatsApp numbers
Connecting returns a Kapso hosted setup link the client opens to finish onboarding; the number is then recorded automatically and its inbound webhook + events are registered — the same as any onboarded number. Binding a number to a workflow is what makes inbound messages reach that agent.
Internal-admin keys additionally have
disconnect_whatsapp_number.
Meta
Errors
Every tool error follows the same shape:{ "error": { "code": "...", "message": "..." } }.