> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# For developers

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.

<Frame caption="Create an MCP key under Integrations and pick its scopes.">
  <img src="https://mintcdn.com/nexor/335V9P_gdO6wPMqv/images/getting-started/integrations-mcp-key.png?fit=max&auto=format&n=335V9P_gdO6wPMqv&q=85&s=f1ece15c77b3d1d91e041bc358e36ebb" alt="MCP Server key creation under Integrations" width="1600" height="900" data-path="images/getting-started/integrations-mcp-key.png" />
</Frame>

<Steps>
  <Step title="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.
  </Step>

  <Step title="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](/docs/en/api/mcp-server).
  </Step>

  <Step title="Ask it to build">
    Describe the agent or the change. Read back the plan and confirm before it mutates anything.
  </Step>
</Steps>

<Note>
  If you are not comfortable with MCP, skip this. NexorGPT inside the dashboard does the same job without any setup. See [Build with NexorGPT](/docs/en/guides/getting-started/build-with-nexorgpt).
</Note>

For your own code, the REST API uses a separate key from the same **Integrations** page. See [Authentication](/docs/en/api/authentication) and the [API reference](/docs/en/api/introduction).

## 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](/docs/en/guides/advanced/overview#mcp-tools).

## Cloud Functions and Scheduled Functions

Both run JavaScript you write inside Nexor. The difference is what starts them.

<Frame caption="The Advanced hub, where functions, tools, jobs, and webhooks live.">
  <img src="https://mintcdn.com/nexor/335V9P_gdO6wPMqv/images/getting-started/advanced-hub.png?fit=max&auto=format&n=335V9P_gdO6wPMqv&q=85&s=11d0da4e3b0abd9de6a7139a594f1d1b" alt="Advanced hub with functions and tools" width="1600" height="900" data-path="images/getting-started/advanced-hub.png" />
</Frame>

|                   | Cloud Function                                                                                              | Scheduled Function                                                                |
| ----------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| Starts when       | A Nexor event happens: a lead changes stage, a meeting is booked, a conversation ends, and more.            | A cron expression fires, in the time zone you set.                                |
| Works on          | The event payload and the lead involved.                                                                    | A cohort of leads selected by a query you preview first.                          |
| Typical use       | Sync a stage change to your CRM, enrich a lead when it arrives, call several APIs when a meeting is booked. | Nightly reconciliation, periodic reminders, batch updates that need custom logic. |
| Before activating | Simulate with a sample payload and inspect the run.                                                         | Preview the cohort, run with safe credentials, check logs.                        |

For structured automations without code, use **Background Jobs**. To only notify an external system of an event, use a **Webhook**. The [Advanced automation overview](/docs/en/guides/advanced/overview#choose-the-right-capability) has the full decision table, and [Cloud Functions](/docs/en/guides/advanced/cloud-functions) has triggers, runtime, and examples.

## Next

Return to the [Launch checklist](/docs/en/guides/getting-started/launch-checklist) to close the setup.