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

# Devin Bot connections and secrets

> Give a Devin Bot its own MCP servers, plugins, sign-ins, and secrets so its sessions can use the tools the job needs.

A [Devin Bot](https://docs.devin.ai/work-with-devin/bots) has its own set of connections and secrets. The sessions it starts use the Bot's connections, not those of the person who happens to be messaging it. This keeps a shared Bot's behavior the same for everyone who uses it.

Each sign-in, plugin, or secret a member gives a Bot is held by the Bot as a grant that the member can take back. See [Access and security](https://docs.devin.ai/work-with-devin/bots/access-and-security.md#how-a-bot-holds-grants) for how that works.

## Connections

A connection is an [MCP server](https://docs.devin.ai/work-with-devin/mcp.md) or a [plugin](https://docs.devin.ai/product-guides/plugins.md) the Bot can use. Manage them on the **Connections** page of the Bot's settings.

* **If you can configure the Bot**, you see everything it is connected to and can add, fix, and remove connections.
* **If you can only use the Bot**, you see only the sign-ins and plugins you gave it yourself, and you can remove them.

### Where a connection comes from

| Scope | Meaning | Can you remove it from the Bot? |
| - | - | - |
| **Enterprise** | Installed for the whole enterprise. Every Bot can use it. | No. Manage it in your enterprise settings. |
| **Organization** | Installed for the whole organization. Every Bot can use it. | No, but you can turn an organization-wide MCP server off for this Bot. You can also remove a member's sign-in given on it. |
| **The Bot's own** | Added to this Bot only. | Yes, with **Disconnect**. |
| **Personal** | A sign-in or plugin that a member gave this Bot. | Yes, with **Remove sign-in** for a sign-in or **Disconnect** for a plugin. |

A plugin that reaches the Bot through another plugin can't be disconnected on its own. Disconnect the plugin that brings it.

### Connection status

Each connection shows whose account the Bot uses there, and a status when something needs attention:

| Status | Meaning |
| - | - |
| **Sign-in required** | Nobody has signed in for the Bot yet. |
| **Sign-in expired** | The sign-in the Bot used is no longer valid. |
| **Not working** | The connection worked before and no longer does, for example because the member who gave their sign-in signed out. |
| **Off for** the Bot | An organization-wide connection that was turned off for this Bot. |

### Add a connection

On the **Connections** page, click **Add connection** and pick an MCP server or plugin. If you already have a working sign-in on that server, the Bot can use your connection, including your sign-in. Otherwise, sign in for the Bot.

* **Connect all your plugins and MCPs** connects the MCP servers you already have sign-ins for and your installed personal plugins at once. The Bot then uses your sign-ins on those servers. A server that already uses another member's sign-in is left as it is.
* **Add account** on a connection gives the Bot a second account on an app it already uses: your own account, or a new one that belongs to the Bot.

### Turn off an organization connection for one Bot

Someone who can configure the Bot can turn an organization-wide MCP server off for that Bot alone, from the connection's menu. The organization's installation and everyone's sign-ins on it stay as they are. The Bot's sessions, including ones that are running, stop using that server.

There is no switch for the Bot's own connections, for enterprise connections, or for a plugin that has no MCP server.

### Sign-ins

Some MCP servers act on behalf of a signed-in user. When a Bot uses one of these, it acts as whoever signed in:

* If you sign in while connecting a server, the Bot acts as you on that server.
* You can let a Bot use a connection you already have, including your sign-in.
* A Bot uses one sign-in per connection. If a server already uses another member's sign-in and it still works, Devin asks before switching the Bot to yours. A sign-in that no longer works is replaced without asking.
* You can give the Bot **its own account**: a separate sign-in, like a service account, so the Bot doesn't act as any one person. This is the better choice for a Bot that several people use.

A sign-in you gave keeps working only while you're a member of the organization and still have that connection:

* If you sign out of the server, the Bot has no sign-in there until you sign back in.
* If you leave the organization or delete your installation of the server, the Bot loses the sign-in.

When you give a sign-in on an MCP server that one of your plugins created, the Bot also gets that plugin and your sign-ins on the plugin's other MCP servers. Taking the sign-in back takes those back too. The plugin loads for the Bot only while you still have it installed.

When the Bot can reach the same server in more than one way, it uses its own connection or sign-in first, then one a member gave it, then your organization's or enterprise's.

> [!WARNING]
>
> Everyone who can use a Bot can reach everything the Bot can reach. Before you give a shared Bot your own sign-in, make sure you're comfortable with every member of that Bot acting through it.

### Requests from the Bot

A Bot can also ask for access while it works. For example, it might ask to use one of your MCP sign-ins, your copy of a plugin, or a personal secret. The request is a card in chat that says what approving will share, and you approve or decline each one. You can remove the access later on the **What it can access** tab of the Bot's **Sharing** page, or by asking the Bot to remove it.

A private Bot, one that only its creator can use, can pick up its creator's sign-ins, plugins, and secrets without asking. A shared Bot always asks the person it is answering. See [Private and shared Bots](https://docs.devin.ai/work-with-devin/bots/access-and-security.md#private-and-shared-bots).

### Personal plugins

Someone who can configure a Bot can give it a plugin from their personal marketplace. The Bot's sessions load the plugin from your copy, so it keeps working only while you still have it installed.

## Secrets

Every Bot already has access to your organization's [secrets](https://docs.devin.ai/product-guides/secrets.md). The **Secrets** page of the Bot's settings holds additional secrets that only this Bot and its sessions can use, for example an API key for a service that only this Bot should call.

* Only members who can configure the Bot see the **Secrets** page, where they add, edit, and delete the Bot's secrets.
* A Bot that isn't shared with anyone can also save, replace, and delete its own secrets from its chat. On a shared Bot, saving a secret from chat needs your approval.
* Personal secrets that members gave the Bot are listed for people who can share the Bot, who can remove them. Anyone the Bot is shared with can use them through the Bot.

## Outposts

When [Outposts](https://docs.devin.ai/cloud/outposts/overview) are enabled, a Bot can choose any Outpost it already has access to for a child session without asking its creator to pick one. Outposts available to the Bot's organization don't need to be shared separately with the Bot.

On the **Outposts** page of the Bot's settings, the creator can share or stop sharing their own personal Outposts (where enabled) and organization Outposts they have permission to share. If a job needs an Outpost the Bot can't already use, it can ask its creator to share one from a card in chat.

> [!WARNING]
>
> Anyone who can message the Bot can have it run commands without approval on any Outpost it can use, including Outposts available through its organization.

## Related pages

* [Devin Bots overview](https://docs.devin.ai/work-with-devin/bots)
* [Access and security](https://docs.devin.ai/work-with-devin/bots/access-and-security.md)
* [Usage limits](https://docs.devin.ai/work-with-devin/bots/usage-limits.md)
* [Devin MCP servers and marketplace](https://docs.devin.ai/work-with-devin/mcp.md)


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