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

# Connect a local agent

> Connect an AI agent on your computer to your Personal Server over MCP, with no tunnel.

Vana Desktop serves a **Local MCP endpoint** for agents on the same computer. The agent reads only the scopes you approve. It works with the tunnel off.

## Requirements

* Vana Desktop, running.
* An MCP client that supports Streamable HTTP and OAuth.

## Find the endpoint

1. In Vana Desktop, open **Settings** > **Server**.
2. Under **Connect apps**, find **Local MCP endpoint**, e.g. `http://127.0.0.1:47321/mcp`.
3. Click the copy button.

Do not hard-code the port.

## Connect Claude Code

Add the server:

```bash theme={null}
claude mcp add --transport http vana <endpoint>
```

Then start the sign-in. Either run `/mcp` in a Claude Code session, or run:

```bash theme={null}
claude mcp login vana
```

Your browser opens. Approve the request in Vana Desktop.

## Connect Claude Desktop

Claude Desktop's custom connectors run through Anthropic's cloud and cannot reach `127.0.0.1`. Use `mcp-remote`, a local bridge, instead. It requires Node.js (`npx`).

1. In Claude Desktop, open **Settings** > **Developer** > **Edit Config**.
2. Add Vana to `claude_desktop_config.json`. Replace the URL with your endpoint:

```json theme={null}
{
  "mcpServers": {
    "vana": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote@0.1.38",
        "http://127.0.0.1:47321/mcp", "--allow-http",
        "--static-oauth-client-metadata", "{\"client_name\":\"Claude Desktop\"}"
      ]
    }
  }
}
```

3. Restart Claude Desktop.
4. Your browser asks to open Vana. Allow it, then approve the request in Vana Desktop.

The `--static-oauth-client-metadata` line makes Vana show **Claude Desktop** as the client name instead of **MCP CLI Proxy**.

Other clients: give it the endpoint and follow its own sign-in steps.

## Approve access

Vana Desktop shows the request:

* **Name provided by client**: the name the agent reports. Vana does not verify it.
* The scopes the agent requests.

Select the scopes to share, then click **Approve and return**. The agent can read only those scopes.

## Revoke access

1. Open **Settings** > **Server**.
2. Under **Connected clients**, click **Disconnect** next to the agent.

Access ends immediately. Your data is not deleted.

## Troubleshooting

**The agent cannot connect.** Vana Desktop must be running. Start it, then retry.

**The agent gets `scope_not_granted`.** You did not approve that scope. To share it, disconnect the agent, connect again and approve the scope.

**Connection refused from another machine.** Expected. The endpoint accepts connections only from the same computer.

**A token stops working on another endpoint.** Expected. A token issued on the local endpoint works only there.

**Claude Desktop says the Vana connector failed to start.** Claude Desktop waits about 60 seconds for the connector. Approve the request in Vana Desktop within that window, or restart Claude Desktop to retry.

**Claude Desktop asks you to sign in again after you disconnect.** Expected. The next time Claude Desktop uses Vana, your browser prompts you to sign in. Cancel it to keep access off, or remove the `vana` entry from `claude_desktop_config.json`.

## Related

* [MCP integration](https://docs.vana.org/applications/mcp.md) — the MCP tools and the third-party path
* [Agents](https://docs.vana.org/applications/agents.md) — how agents use grants


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.