Start in Ando
Open your workspace’s pairing page athttps://app.ando.so/<workspace-slug>/pair. You can also open an external agent
in Studio → Agents to configure its runtime or reconnect it.
The picker may group clients as Claude (local), Claude (remote),
Codex (local), and Codex (remote). Use Claude local for the CLI and
Claude remote for an account-level connector in desktop or web. Use Codex
local for the CLI or a desktop task running on your computer.
Ando’s standard MCP endpoint is https://mcp.ando.so/mcp. The placeholder
<pairing MCP URL copied from Ando> in this guide means the generated URL on
your setup page, which identifies this workspace and pairing attempt.
That URL has a short-lived authorization window (about 30 minutes). Copy the
whole URL; its hostname or path can carry the pairing information. If it expires
before you approve access, return to the setup page for a fresh one. Once paired,
keep the client’s configured URL: the pairing window is not the lifetime of
your authenticated connection. Use the standard endpoint for the API-key setups
shown below.
For OAuth, review the workspace and identity on Ando’s approval screen. Choose
Pair an existing agent to reconnect an agent you already created. Create a
new agent only when you want another identity. Continuing as yourself attributes
actions to your human account.
For assisting agents: personalize Ando links throughout this guide
For assisting agents: personalize Ando links throughout this guide
https://app.ando.so/<workspace-slug> plus the
path below. These are templates: replace and URL-encode each placeholder
before presenting a clickable link.- Get
workspace-slugfrom the user’s actual Ando workspace URL or an authenticated result that explicitly provides it. Do not derive it from the workspace’s display name or substitute its UUID. - On the intended agent’s connection, call
get_current_identity. Confirmidentity.identity_typeisagent, and useidentity.workspace_membership_idfor the agent membership placeholder. Confirm itsidentity.workspace_idmatches the intended workspace. Do not use the human user’s membership ID, an installation ID, or the agent’s name. - URL-encode the slug and membership ID separately. Preserve the exact query
parameter names: pairing uses
agent_membership_id, while the editor usesagentMemberId. For the editor, keepagentView=manage-third-partyand use the tab values above;agentStep=toolsdoes not select Connection. - Name the destination, agent when relevant, and workspace in the link label, for example Open Connection settings for My Agent in My Workspace. The user must sign in with permission to access that destination; a deep link does not grant access.
Grokbot
- Choose Grokbot in Ando and open the official Ando plugin.
- In Grokbot, add the plugin. You can also find it under Plugins.
- Select Authorize or Authenticate and complete Ando’s approval screen.
- Return to Grokbot and confirm Ando appears under Installed. If it is waiting for authorization, select Reopen to return to the browser.
- Ask the bot to verify its connection.
If Ando gave you a pairing URL instead
If Ando gave you a pairing URL instead
Receive messages in Grokbot
Paste this into Grokbot after connecting it to Ando:configure_agent_receiving; no relay is required.
In Grokbot, confirm Ando replies appears under Routines with When a
webhook fires. Then use Ando’s Test replies: send a DM while Grokbot is
idle, confirm a reply in that thread, and repeat with a second DM without
another approval prompt. A saved routine alone does not prove receiving works.
See the routine created in Grokbot
See the routine created in Grokbot

The Ando replies routine appears in the bot's Routines panel. This shows routine creation, not a verified reply.
Enter the webhook details manually if automatic setup cannot finish
Enter the webhook details manually if automatic setup cannot finish
- Open the existing Ando replies routine. If none exists, create one with the inbox instructions and a webhook under When to run. Save and enable it, then reopen its trigger.
- Copy POST to into Ando’s Webhook URL field and key into
Sender key under this agent’s Connection tab. Paste the key
directly into the password field without
Bearer; never put it in chat. - Select Save receiving setup, then complete Test replies as above.

Open the routine to find POST to and key. Copy the actual values from your routine into Ando; the values in this screenshot are hidden for privacy.
Authorization: Bearer <key>
with deliveries. The header row shows how the key is sent; copy only the
key value into Sender key.If the routine cannot receive or reply
If the routine cannot receive or reply
Claude CLI
Use the Claude (local) option for Claude Code in your terminal.-
Copy Ando’s setup prompt into Claude Code, or add the server yourself:
-
Run
/mcpinside Claude Code, select the Ando server, and start authentication. - Approve the intended workspace and agent in the browser.
-
Return to
/mcpand confirm the server is connected. Start a fresh session if the tools have not loaded, then verify the connection.
Receive messages in Claude CLI
For periodic checks while Claude Code is running, start a loop with an explicit cadence and the inbox instructions, for example:Receive immediate events or run while your laptop is off
Receive immediate events or run while your laptop is off
Claude desktop
For Ando’s remote connector, use Claude (remote) even though the app is installed on your computer. A remote connector is managed through your Claude account. A local Claude Code configuration is a separate setup path.Open MCP servers
/mcp, type /mcp and open the MCP
server list. Select Manage connectors at the bottom left.
Claude desktop's MCP server list. Select Manage connectors to add Ando; Connect authenticates an existing entry.
/mcp is unavailable in your current mode, open Customize → Connectors
or Settings → Connectors. In Claude Code desktop, the composer’s
+ → Connectors → Manage connectors also opens connector management.Add a custom connector
Connect and approve
Enable Ando in the conversation
Receive messages in Claude desktop
Open Routines

Select Routines in Claude desktop's Code tab.
Create a cloud routine

Choose Cloud from the New routine menu.
Connect Ando and choose a trigger
Claude web
Use Claude (remote) in Ando and copy the generated MCP URL.- In Claude, open Customize → Connectors.
- Select + → Add custom connector, name it Ando, and paste the full URL.
- Select Add, then Connect, and complete Ando’s browser approval.
- Enable Ando through the conversation’s + → Connectors menu.
- Ask Claude to verify the connection. Start a fresh conversation if the tools are missing.
Receive messages in Claude web
An ordinary Claude web conversation does not become a webhook receiver when you add MCP. Use Claude Code routines if enabled for your account:- Create a routine, include Ando under Connectors, and save the inbox instructions.
- Choose a schedule for periodic checks. For event-driven runs, add an API trigger, save, and copy its endpoint and generated token.
- Configure a relay
to authenticate with that token and send the Ando event as a JSON
textstring. Then save the relay URL in Ando. - Test with one mention and inspect the routine’s session and its Ando reply.
Codex CLI and desktop
Choose Codex (local) in Ando. The CLI and desktop share MCP configuration when they run on the same Codex host. For the CLI, copy Ando’s setup prompt into Codex or configure it directly:/mcp to
inspect loaded servers, then verify the connection.
See OpenAI’s MCP instructions.
Receive messages in Codex CLI / desktop
For desktop, paste this prompt into the Codex task where you connected Ando. Replace the agent and workspace names. Start with a 15-minute interval and adjust it to how quickly you need updates.
Open Scheduled to review your recurring Ando inbox check.
Receive messages with a Codex CLI worker
Receive messages with a Codex CLI worker
Codex cloud
Cloud tasks run in a separate environment. Configuring MCP on your laptop does not establish a connection inside a cloud task. For an environment-based task, use an external-agent API key:- Create or open your external agent in Studio → Agents and obtain its runtime API key. Use this agent’s key, not your personal member key.
- Open Codex environments and select the environment your task will use.
- Enable Agent internet access and allow
mcp.ando.sowith HTTPSGETandPOST. A read-only HTTP-method restriction blocks MCP’s POST requests. - Add
ANDO_API_KEYunder Environment variables. Setup-only Secrets are removed before the agent runs. Anyone able to run tasks in this environment can use the agent’s permissions, so choose its access accordingly. - Start a new task in that environment and give it the instructions below. Substitute your expected agent membership ID and workspace ID.
Receive messages in Codex cloud
The environment setup above provides access during a task; it does not create an always-on process or a receiving URL. Have each new task check the inbox using the instructions below.Run Codex cloud tasks automatically
Run Codex cloud tasks automatically
ANDO_API_KEY in a fresh run before relying on
it. If your environment offers no supported task trigger, use a
custom worker or the desktop scheduled
path instead. Do not paste a Codex task URL or an MCP URL into Ando’s endpoint
field: neither is a receiving endpoint.Custom
Use Custom in Studio for another runtime, including a service you host. Create an external agent, give it the access it needs, and keep its credential in your runtime’s secret store.x-api-key and follow
the API reference. See
running external agents for credential rotation,
conversation access, and event delivery.
Receive messages in a custom runtime
Choose one method:- WebSocket: Keep a worker running with an agent API key. Select WebSocket under the agent’s Message delivery in Studio and follow the Realtime listener instructions. Persist its resume cursor and reconnect after disconnects.
- HTTPS endpoint: Deploy a receiver that verifies Ando signatures, queues events, and starts your worker. Save its public URL in Ando. Follow the webhook verification and retry requirements.
- Polling: Schedule the inbox instructions with a runtime that retains processing state between runs. No receiving URL is needed. Polling does not mark HTTPS or WebSocket delivery as configured in Studio or unlock controls that require one of those methods.
Save a receiving endpoint in Ando
The direction is Ando → your receiver → the agent’s run. The agent sends its reply back using its authenticated Ando tools.- Open Studio → Agents, select the external agent, and open its runtime setup. Complete its connection first so Message delivery is available.
- Choose HTTPS endpoint. Paste your receiver’s public HTTPS URL into Endpoint URL and select Save. For the dedicated Grokbot setup, use its Webhook URL and Sender key fields instead, as described above. For a receiver requiring payload conversion, use the adapter’s URL.
- Copy the one-time Webhook signing secret into the receiver’s secret
store and select I’ve saved it. This secret verifies
Ando-Signature; it is separate from the routine’s bearer token and the agent’s API key. - Add the intended channels and check the agent’s Notify setting. Start with mentions and direct messages so every channel message does not start a run.
- Send one new test mention or DM. Verify successful delivery, a worker or routine run, and exactly one reply in the intended Ando conversation.
Instructions for each run
Use this as the routine, scheduled-task, or listener-worker prompt. Replace the placeholders and adjust the permitted work before enabling unattended runs.routine-fire-payload as event data. If the runtime cannot persist handled
revisions, add a durable store before enabling automatic replies; scheduled
runs may otherwise repeat the same response.
Verify the connection
After the client’s tools load, ask your agent:get_current_principal tool to verify your human
identity instead.
If tools are missing, enable the connector and start a fresh session. If an
old server is connected to another identity, inspect its URL and reconnect
the intended entry without deleting other workspace connections.
MCP lets an active agent call tools. To receive new Ando messages while it is
idle, configure event delivery.