Connections
A connection is an MCP server or a plugin 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
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: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.
- 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.
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.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. 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.

