Connect an AI client

1. Create an MCP server in NexaCloser

1. In the app, open MCP servers in the sidebar (also under Settings → API → MCP Servers).
2. Click New MCP server and name it after the client, for example Claude Desktop.
3. Tick Read-only if the client should only read data. It can then list and look up, but never send messages or change anything.

Make one MCP server per client. You can revoke each one on its own, see when it was last used, and limit it to certain tools.

2. Add NexaCloser to your client

Claude (claude.ai and Claude Desktop)

1. In Claude, open Settings → Connectors and add a custom connector.
2. Paste https://api.nexacloser.com/mcp as the URL and connect.
3. A NexaCloser page opens. Sign in, pick the MCP server you created and click Authorize.

No key to copy: the connector signs in with OAuth and refreshes its own access.

Claude Code

claude mcp add --transport http nexacloser https://api.nexacloser.com/mcp

Then run /mcp inside Claude Code, pick nexacloser and sign in when the browser opens.

Cursor

Open the MCP server in NexaCloser, click Create token and copy the mcps_… token. Then add this to ~/.cursor/mcp.json (or Cursor Settings → MCP → Add new server):

{
  "mcpServers": {
    "nexacloser": {
      "url": "https://api.nexacloser.com/mcp",
      "headers": { "Authorization": "Bearer mcps_YOUR_TOKEN" }
    }
  }
}

If your Cursor version signs in to remote servers with OAuth, you can leave out headers and sign in the same way as in Claude.

Make, n8n, scripts and other clients without OAuth

Use the MCP server’s token (mcps_…) as a Bearer token, exactly like the Cursor example. It carries the MCP server’s read-only setting and tool limits.

Clients that only run local (stdio) servers

Bridge them with mcp-remote:

{
  "mcpServers": {
    "nexacloser": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.nexacloser.com/mcp",
               "--header", "Authorization: Bearer ${NEXACLOSER_MCP_TOKEN}"],
      "env": { "NEXACLOSER_MCP_TOKEN": "mcps_YOUR_TOKEN" }
    }
  }
}

3. Check it works

Ask the client something only your CRM knows, for example “How many contacts did we get this week?”. Or call the server yourself:

curl -s https://api.nexacloser.com/mcp \
  -H "Authorization: Bearer $NEXACLOSER_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The answer lists every tool the token may use.

Troubleshooting

Symptom	Cause and fix
The sign-in page says you have no MCP servers	Create one first (step 1), then connect again.
401 / Unauthorized	The token or key is wrong, rotated or revoked, or the MCP server was revoked.
Tool … requires scope mcp:write	The MCP server is read-only. Make a read + write one for this client.
Tool … is not in this MCP server’s allowed tools	The MCP server has Restrict Tools on. Allow the tool on its page.
requires the … connection	The MCP server’s connection limits, or the workspace has not connected that service (Google, Meta, TikTok, WhatsApp, SMS).