# Connect your AI (MCP)

Your AI (Claude Desktop, Cursor, or an agent you wrote) connects to the gateway with your token; the tool list is trimmed to your permissions — connecting an AI never widens access.

## Remote MCP

Add a server to your MCP client's config: the URL is this site's `/mcp`, with your token in the header.

1. Exchange channel code + secret for a token (`POST /api/v1/auth/token`).
2. Paste the JSON on the right into the client config and replace the token.
3. Once connected the tool list appears automatically; what you can call depends on your roles and warehouse allowlist.

```json
{
  "mcpServers": {
    "ever-api": {
      "url": "https://connect.everugg.net.au/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}
```

MCP is not split per endpoint: once connected, the tool list is given according to your permissions. This config applies to every endpoint.

## Command-capable AI: use the CLI

Coding assistants like Claude Code and Cursor already live in a terminal: with `ever` installed they look up stock and read the docs on their own, no MCP setup. Tool names are identical to MCP (both come from the capability catalog).

```bash
curl -fsSL https://connect.everugg.net.au/cli/install.sh | sh
ever login --sandbox
ever tools --json
```

The docs are shaped for AI too: every page has a Markdown version, and the index is https://connect.everugg.net.au/llms.txt?lang=en

## Permissions

Every connection uses the caller's own token: we resolve who you are and your scopes, then trim the tools; every call still goes through the gateway (auth, authorization, warehouse allowlist, rate limit). Writes are never executed automatically.

## A2A (agent to agent)

A peer agent can talk directly over the A2A protocol: `POST https://connect.everugg.net.au/a2a` · https://connect.everugg.net.au/.well-known/agent-card.json

---
Markdown source: https://connect.everugg.net.au/reference/mcp.md?lang=en · Web page: https://connect.everugg.net.au/reference?sec=mcp&lang=en