Skip to main content
Nothing in this walkthrough requires a developer. But if you have one, this page is the part of onboarding the Nexor team covers with technical customers: how to manage Nexor from your own AI client, and which automation primitive to use for what.

Manage Nexor from your AI client (MCP)

Nexor exposes its account-management capabilities as an MCP server. Once connected, Claude, Cursor, Codex, or any MCP client can create and edit agents, upload leads, inspect conversations, and configure automation, all in chat.
MCP Server key creation under Integrations

Create an MCP key under Integrations and pick its scopes.

1

Create a key

Open Integrations from your profile menu, go to MCP Server, and create a key with the scopes it needs. Start read-only if you are still exploring.
2

Connect your client

Add the server to your client with the key in the X-API-Key header. Exact commands and config snippets for each client are in the MCP Server guide.
3

Ask it to build

Describe the agent or the change. Read back the plan and confirm before it mutates anything.
If you are not comfortable with MCP, skip this. NexorGPT inside the dashboard does the same job without any setup. See Build with NexorGPT.
For your own code, the REST API uses a separate key from the same Integrations page. See Authentication and the API reference.

Let the agent call your systems (MCP tools)

MCP tools go the other way: they let a Nexor agent call your API during a conversation, for example to check inventory, look up a customer, or calculate a price. Define the HTTP call once in the Advanced hub, assign it to an agent, and optionally restrict it to certain pipeline stages or run it before the first message. Environment variables keep tokens out of the tool definition. See MCP Tools.

Cloud Functions and Scheduled Functions

Both run JavaScript you write inside Nexor. The difference is what starts them.
Advanced hub with functions and tools

The Advanced hub, where functions, tools, jobs, and webhooks live.

For structured automations without code, use Background Jobs. To only notify an external system of an event, use a Webhook. The Advanced automation overview has the full decision table, and Cloud Functions has triggers, runtime, and examples.

Next

Return to the Launch checklist to close the setup.
Last modified on September 7, 2026