Remote MCP access

Remote access gives an agent that isn't on your computer an MCP URL and a token, so it can see your panes and message them. It reaches your computer through the AgentGrid relay, the same way the phone app does. It's in beta.

You need to be signed in to AgentGrid, and the background service must be running (see System tray and daemon).

Create a token

1. Open Settings → MCP Server and find Remote access (beta).
2. Select Create token.
3. Copy the URL (it starts with https://agentgrid-relay.agentgrid.workers.dev/v1/mcp/) and the token. The token is shown once; after you select I’ve saved it it can't be shown again. Create a new one if you lose it.

We may add a shorter branded address later; URLs you've already set up will keep working.

Each token belongs to this computer. Create one per agent, so you can cut one off without touching the others. Settings lists each token by its ID, the start of the token (like agr_536d5ac7), and when it was created, so you can match it to the agent you gave it to.

Connect an agent

Grok Bot: add a custom MCP server with the URL, and add the header Authorization: Bearer <token>.

Claude Code on another machine:

claude mcp add --transport http agentgrid <url> --header "Authorization: Bearer <token>"

Any MCP client that speaks Streamable HTTP and can send that header works the same way. claude.ai connectors aren't supported yet, because they need OAuth.

What a remote agent can do

Remote agents get seven tools: list_tabs, list_panes, search_panes, read_pane, send_message, wait_for_pane and wait_for_any. They can't type into terminals, or open, close or move panes.

Security

• Requests travel over TLS to the AgentGrid relay and on to your computer. The relay can read them: they are not end-to-end encrypted, unlike the phone app.
• The relay doesn't check or store your token; your computer does, on every request.
• OAuth and end-to-end encryption are planned.

Revoke a token

Select Revoke next to the token's ID in Remote access (beta). The next request with that token is refused. When the last token is revoked, your computer stops holding the relay connection open. After that, remote callers get a "desktop is offline" error rather than an authorization error.