> ## 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.

# MCP servers

> Compare file, event-log, Internet-content, and XMPP tools exposed by a Neuron

Each MCP server exposes one capability and has its own OAuth scope and Neuron privileges. Connect only the server your AI application needs.

<Warning>
  Enabled servers and tool counts differ by deployment. Use the MCP discovery response from your Neuron instead of assuming every item below is available.
</Warning>

| Server           | Endpoint        | Tools | Resources                    | Prompt                     |
| ---------------- | --------------- | ----: | ---------------------------- | -------------------------- |
| Event Log        | `/MCP/EventLog` |     9 | No                           | Find Sensitive Information |
| Internet Content | `/MCP/Content`  |     5 | No                           | —                          |
| File Storage     | `/MCP/Files`    |     9 | Account files                | —                          |
| XMPP             | `/MCP/XMPP`     |    10 | Roster contacts and messages | —                          |

## Select the smallest server

Connect an agent only to the server it needs. There is no joined `/MCP` endpoint.

## Tool annotations

Neuron declares MCP safety hints on each tool:

* whether it can modify the environment;
* whether it can destroy data;
* whether repeated calls are idempotent;
* whether it accesses the open world.

These annotations help a client plan tool calls; they do not grant access. Authentication and Neuron privileges determine what the account can do.

## Resource isolation

File and XMPP resources are account-specific and require authentication. A resource URI obtained by one agent must not be treated as a shareable public URL.

## Extension model

Packages can register additional `HttpMcpServerResource` implementations. An extension should publish its own OAuth resource name, scope root, narrow privilege leaves, and accurate safety annotations. See [Build an MCP server](/mcp/build-a-server).