Connect Your Agent

Connect your agent app with one URL and a browser sign-in, then check the connection.

On This Page

Connect your agent app, such as Claude Code or Codex, using Model Context Protocol (MCP). MCP lets the app use Agent Connect tools. Every agent uses the same MCP URL, /mcp on this app. You choose the agent when you sign in, not in the URL.

Choose your app under Connect your agent on the home page, in the last step of the setup wizard, or on the dashboard’s Connect page. On the dashboard, the app’s button opens its setup instructions. For Claude, Codex and Grok, also choose where you use the app. Terminal apps get a command, desktop and cloud agents get a prompt to paste into their chat or the exact settings path, and every other app gets the URL and a prompt.

How Connecting Works

Add the Agent Connect MCP URL to your app.
The app opens your browser. Sign in to Agent Connect.
Choose which agent the app should use, or create a new one on the same screen, and which of its accounts it can reach.
Complete the signature request for each selected account using the wallet or passkey you signed in with.
The app is connected. Ask it: “What are my Agent Connect balances?”

No key is pasted into a prompt or a chat. The screen shows Connected with the app’s name once the app is bound to your agent.

Choose an App

Your app	How to add the URL	Guide
Claude Code (terminal or the desktop app’s Code tab)	`claude mcp add --transport http --scope user agent-connect <URL>`, then `/mcp`	Connect Claude Code
Claude Desktop, claude.ai and Cowork	Customize → Connectors → Add custom connector	Below
Codex CLI	`codex mcp add agent-connect --url <URL>`	Connect Codex
Codex desktop app	A prompt that adds the server, then Settings → MCP plugins → Authenticate	Connect Codex
Cursor	Add to Cursor button, or `~/.cursor/mcp.json`	Below
Grok Bot, grok.com or Grok Build	A prompt, a custom connector, or `grok mcp add`	Below
Hermes	`hermes mcp add agent-connect --url <URL> --auth oauth`	Below
OpenClaw, Centaur, or another compatible app	A prompt, or the URL in the app’s MCP settings	Custom MCP Clients

Replace <URL> with the MCP URL shown in Agent Connect, for example https://<your-agent-connect-host>/mcp.

Cursor

Choose Add to Cursor in Agent Connect, or add this to ~/.cursor/mcp.json:

{ "mcpServers": { "agent-connect": { "url": "<URL>" } } }

Then connect the server in Cursor’s MCP settings. Your browser opens so you can sign in.

Claude Desktop, claude.ai and Cowork

Open Customize → Connectors.
Choose Add → Add custom connector.
Enter a name and paste the MCP URL.
Sign in when asked.

The connector belongs to your Claude account, so chats, Cowork tasks and the desktop app’s Code tab all use it. On Team and Enterprise plans an owner adds it under Organization settings → Connectors and each member then selects Connect. Claude connects from Anthropic’s cloud, so the URL must be reachable from the public internet. A local or private address does not work.

Claude in the Claude app, claude.ai and Cowork may decline to run tools that move money (swaps, transfers and withdrawals), even when the account’s rules allow them. This comes from the Claude app, not from Agent Connect. It can still read balances, history, rules, quotes and previews. To run payments, connect Claude Code or another client.

Grok

Grok Bot: paste the prompt from the Grok Bot tab into a Grok Bot chat and open the sign-in link it gives you. To add it yourself, open the bot’s details, then Plugins → Add plugins → Add custom, and paste the URL.
grok.com: open grok.com/connectors, choose New Connector → Custom, paste the URL and sign in.
Grok Build: run grok mcp add --transport http agent-connect <URL>, then in grok type /mcps, select agent-connect and press i to sign in.

Grok Bot and grok.com connect from xAI’s cloud, so the URL must be public.

Hermes

Run this, and keep all tools enabled when Hermes asks:

hermes mcp add agent-connect --url <URL> --auth oauth

Your browser opens so you can sign in. If it does not, run hermes mcp login agent-connect, or add --flow device on a server without a browser. In a Hermes session that is already open, type /reload-mcp.

Test the Connection

Ask your app: “What are my Agent Connect balances?” It should list your accounts and their balances. A zero balance is still a successful check.

Connected means Agent Connect has bound the app to your agent. Account permissions and spending rules still apply to every request.

Use an API Key Instead

OAuth sign-in is the default. If your agent cannot open a browser, for example one running headless on a server, open API Key in the dashboard’s Agent Integrations. Choose your app to open its setup window, name the key and select the accounts it can use.

You complete one signature request per account. The key lasts 30 days.
The key is shown once. Replace it from the dashboard if you lose it.
Keep the key in an environment variable named AGENT_CONNECT_KEY and reference the variable in your app’s configuration. Never paste the key into a prompt or commit it.
A key is bound to the agent it was issued for. Keys and OAuth sign-ins can be used side by side.

See Connect Claude Code and Connect Codex for the exact settings, or Custom MCP Clients for the Authorization header.

Manage Access

The dashboard lists each connected app. Choose Disconnect to revoke an app’s access. For each account, you sign the grant revocation. Other connections keep their access.

If the app does not connect, see Troubleshooting. For tool details, see MCP Tools.