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

# Choose your Neuro integration

> Select an SDK, the Agent API, MCP, direct XMPP, or a Neuron package

Choose the interface that matches where your code runs and who controls credentials and private keys.

## Decision guide

```text theme={null}
Building a backend or service?
        ├── A supported SDK exists for your language and Neuron version
        │       └── Use the SDK
        └── No supported SDK exists
                └── Use the Agent API directly

An AI model needs bounded tools?
        └── Use MCP

Need direct XMPP semantics and client-managed keys?
        └── Use XMPP

Adding a server-side Neuro capability?
        └── Build a Neuron package
```

## Compare the options

| Integration    | Use it when                                                                           | Who manages credentials and keys                                                                | Start                                                  |
| -------------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| Supported SDK  | The SDK page marks a library Supported for your language and Neuron version           | Uses the authentication model documented by the SDK                                             | [Check SDK status](/developer-tools/sdks)              |
| Agent API      | A backend needs Neuro's primary HTTP interface                                        | The application acts through an agent rather than holding the keys used by a direct XMPP client | [Agent API Quickstart](/neuron-api/quickstart)         |
| MCP            | An AI system needs explicitly scoped, model-callable tools                            | OAuth scopes and Neuron privileges bound the available tools                                    | [MCP overview](/mcp/overview)                          |
| Direct XMPP    | The client requires direct protocol semantics and manages its own keys and connection | The direct client holds and manages its keys                                                    | [XMPP and email](/protocols/xmpp-and-email)            |
| Neuron package | The capability must run inside and extend a Neuron                                    | Package signing and Neuron privileges govern installation and execution                         | [Neuron development](/neuron-development/introduction) |

<Warning>
  The term **Agent API** is unrelated to AI agents. It is the name of Neuro's main HTTP API.
</Warning>

## Browser and mobile applications

Do not embed an Agent API creation secret in a browser or distributable mobile application. Use an application backend for trusted operations and the dedicated browser onboarding/session flow when the user must interact directly with the Neuron.

```text theme={null}
Browser or mobile app
        ↓
Application backend
        ↓
SDK or Agent API
        ↓
Neuron
```

See [Browser-based signup](/neuron-api/guides/browser-based-signup) for the web-form and session-token flow.

## API reference examples

API reference pages use cURL so you can see the complete HTTP request without installing a language package. Before choosing an SDK, confirm its support status and compatible Neuron version.