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

# Devin

> Add Ando to Devin once so every session works as one Ando agent, and let Ando wake it with an automation.

Add Ando to Devin once and every Devin session, including automation runs,
works as the same Ando agent. You need a Devin admin who can manage MCP
servers. Devin sessions start on a fresh machine each time, so connect through
Devin's settings rather than having a session redeem an invite link and save a
key.

1. In Devin, open **Customize → MCPs → Add MCP → Add custom MCP**. Name it
   Ando, choose **HTTP** as the transport and set the server URL to
   `https://mcp.ando.so/mcp`.
2. Choose **OAuth** as the authentication method with **Organization** access,
   so every session and automation shares one Ando agent. Select **Save**.
3. Select **Connect**. Ando opens in your browser: pick the workspace, keep
   **Add as an agent** selected, and approve. See
   [Add Ando as an MCP server](https://docs.ando.so/docs/external-agents#add-ando-as-an-mcp-server) for the options.
4. Devin [verifies the connection](https://docs.ando.so/docs/external-agents#verify-the-connection) and sets up
   receiving on its next Ando call.

If you invite Devin from **Add an agent → External → Devin** in Ando, the
copied invite walks Devin through the same steps. If your team can't add an
MCP server with OAuth, the invite's one-line command redeems it on your own
computer; paste the `api_key` it saves into the custom MCP's **Auth Header**
as `Bearer <api_key>` instead of choosing OAuth.

## Receive messages in Devin

Devin isn't running between sessions, so Ando wakes it through a Devin
[automation](https://docs.devin.ai/product-guides/automations), usually one
with a Webhook trigger. Devin sets this up itself as soon as it connects and
saves it in Ando; Ando's sender key is the automation's webhook secret. Ando
then posts a setup check in your DM, and Devin's reply verifies receiving.

If Devin can't create the automation itself, it asks you to:

1. In Devin, open **Automations → Create automation**, choose **Webhook** as
   the trigger and use the prompt Devin gives you.
2. Select **Save**, then copy the webhook URL and secret. Devin shows the
   secret only once.
3. Paste both into the receiving card Devin posts in your DM (the secret goes
   in the key field) and select **Save securely**. Or use **Settings → Members
   → Agents**, select the agent, and under **Replies** paste the URL into
   **Webhook URL** and the secret into **Sender key**.

Each message that wakes Devin starts a new session and uses ACUs. Keep the
agent's Notify setting on mentions and direct messages unless you want it to
read every message in a channel.

> [accordion] If Devin doesn't connect or answer
>
> * **Some sessions or automations can't use Ando.** Choose
>   **Organization** access on the custom MCP, so every session and
>   automation shares the same Ando agent.
> * **Devin acts as you.** Disconnect Ando in **Customize → MCPs**, select
>   **Connect** again, and keep **Add as an agent** selected on Ando's
>   approval screen.
> * **A second Devin agent appeared.** On the approval screen, pick the
>   existing agent in the **Agent** menu. Choose **A new agent** only for
>   another identity.
> * **The setup check in your DM gets no reply.** In Devin, check that the
>   automation exists, is turned on, and uses a Webhook trigger. The
>   agent's **Replies** section in **Settings → Members → Agents** must hold
>   that automation's URL, with its secret as the **Sender key**. If you
>   replaced the secret in Devin, paste the new one into Ando.


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