> ## Documentation Index > Fetch the complete documentation index at: https://docs.vybe.build/llms.txt > Use this file to discover all available pages before exploring further. # Connections overview > How Vybe connects AI coworkers and apps to your team's tools and data Connections link Vybe to the tools and data your team already uses: SaaS apps, MCP servers, your own APIs and your databases. Once something is connected, your AI coworkers can read and act on it, and your apps can use it in their code. ## Where you manage connections There are two places, and they show the same connections. **Connections** in the sidebar is the everyday view. It has a search box and three tabs: | Tab | What it shows | Button to add one | | - | - | - | | **Integrations** | Accounts you've connected for third-party apps | **Connect integration** | | **MCP** | MCP servers you've connected | **Connect MCP** | | **Advanced** | **Custom APIs**, **Organization Databases** and **External Databases** | **Add Custom API**, **Create database**, **Connect database** | Click a connected account to see who can use it, when it was connected and by whom, and to disconnect it. **Settings → Data** has a more detailed view. Open the user menu at the bottom of the sidebar, choose **Settings**, and look under **Data**: **Integrations**, **MCP Servers**, **Custom APIs**, **Databases** and **Data queries**. These pages show tables with more detail, such as who connected each account and its visibility. Each integration account also has a **Settings** button, where you set a display name, fill in app-specific settings and, for Private accounts, give coworkers access. SSH keys (under **Databases**) and data queries are only managed here. ## Types of connections | Type | What it connects | How you set it up | Good for | | - | - | - | - | | [Integrations](https://docs.vybe.build/connections/integrations.md) | 3,000+ apps from the catalog, plus a few native integrations | Sign in to the app, or paste an API key | Everyday tools: CRM, project tracking, docs, support, billing | | [MCP servers](https://docs.vybe.build/connections/mcp-servers.md) | Remote MCP servers, from a built-in catalog or your own URL | Public, token or OAuth | Services that publish an MCP server | | [Custom APIs](https://docs.vybe.build/connections/custom-apis.md) | Any REST API that uses a static key or token | Enter the key and choose how it's sent | Internal APIs and services that aren't in the catalog | | [External databases](https://docs.vybe.build/connections/databases.md) | Your PostgreSQL or MySQL database (Amazon Redshift with help from support) | Paste a database URL, optionally through an SSH tunnel | Live production or analytics data | | [Organization databases](https://docs.vybe.build/connections/databases.md#organization-databases) | A shared Postgres database that Vybe hosts for your organization | Give it a name | Shared tables that coworkers and apps read and write | | [Data queries](https://docs.vybe.build/connections/data-queries.md) | A saved SQL query against one of your external databases | Write and name the query | Reusable queries that apps and coworkers run by name | ## Who can add connections Everyone in your organization except Guests can add connections: Owners, Admins, Editors and Viewers. Guests can't open the Connections page or the **Data** settings pages. ## Who can use a connection Each integration account and MCP account has a visibility setting: * **Private** (the default): "Only you can use this connection." You can still give your coworkers access to it. * **Organization**: "Everyone in the organization can use this connection." To change it, open **Connections**, click the account and pick an option under **Who can use *name***. You can also change it in the **Visibility** column under **Settings → Data → Integrations**. > [!NOTE] > > The account's settings dialog calls the Private option **Restricted** ("Only you and the agents you grant access to can use this integration."). It's the same setting. The other connection types work differently: * **Custom APIs** have a **Scope**: **Organization (all apps)** or **Specific Apps**. * **External databases** apply to your whole organization. * **Organization databases** are shared with your whole organization. * **Data queries** are visible to your whole organization. ## Who can change or disconnect a connection Only the person who connected an integration or MCP account, or an Owner or Admin, can change its visibility or settings, or disconnect it. The same rule applies to editing and deleting a data query: its creator, or an Owner or Admin. To disconnect an account, open **Connections**, click the account, click **Disconnect *name***, then confirm with **Delete**. This permanently deletes the account. If any triggers use it, the dialog warns you that they'll be deleted too. Apps that call the account stop working. AI coworkers can't disconnect accounts. If you ask one to, it tells you how to do it yourself. ## How an AI coworker gets access A coworker starts with no access to any integration account, MCP account, custom API or external database, including Organization ones. Someone has to turn on each connection for each coworker. Organization databases are the exception: a coworker's **Organization Databases** capability is on by default. See [Databases](https://docs.vybe.build/connections/databases.md#organization-databases). ### Access levels | Level | What the coworker can do | | - | - | | **Full access** | Use every action the connection offers | | **Read only** | Use only actions that read data. Actions that create, change, delete or send are blocked. | | **Custom** | Use only the actions you pick, grouped as **Read-only** and **Write / Delete** | | **Off** | Nothing. The coworker can still ask you for access. | Custom APIs are either on (**Full access**) or off. ### Three ways to give access 1. **From the coworker's Connections section.** Open the coworker and go to **Connections**. The **Integrations** and **MCP** tabs list Organization accounts and your own Private accounts. Turn on the switch next to an account, then choose an **Access level**. The **Advanced** tab has the **External Databases** and **Organization Databases** switches and a switch for each Organization-scoped custom API. 2. **From the account's settings.** Under **Settings → Data → Integrations**, click **Settings** next to a Private account, then **Agent access → Add agent** and pick the coworker. The same dialog opens right after you connect a new account. 3. **In chat.** When a coworker needs a connection it doesn't have, it asks for it. In the coworker's chat in Vybe, a **Grant access to *name*** card appears with an access level picker and an **Approve** button. In Slack, the coworker posts a card with **Approve** and **Deny**. In other places it sends you a link to approve in Vybe. If the coworker asks you to connect a new account from its chat, connecting gives it access right away. If you already have a matching Private account, the card shows a **Grant** button instead. ### Starting access level The access level a coworker starts with depends on how you gave access: | How you gave access | Starting level | | - | - | | Turned on an Organization account in the coworker's **Connections** | **Full access** | | Turned on your own Private account in the coworker's **Connections** | **Read only** | | **Agent access → Add agent** in the account's settings | **Full access** | | Connected an account, or clicked **Grant**, on a connect card in the coworker's chat | **Full access** | | Created a custom API from the coworker's **Add *service* as a custom API** card, with **Organization (all apps)** scope | **Full access** | | Approved a request in chat | The level you pick. It starts at the level the coworker asked for. | You can change the level at any time from the coworker's **Connections** section. ### Who can give access * The coworker's owner, and people with Editor or Admin access to the coworker, can turn connections on or off and change access levels. See [Sharing and access](https://docs.vybe.build/coworkers/sharing-and-access.md). * Only the person who connected a Private account can share it with a coworker. Other people don't see your Private accounts. > [!TIP] > > Give each coworker the least access it needs. A coworker that writes reports only needs **Read only**. ## How apps use connections Apps can call integrations, custom APIs, databases and data queries from their code. The AI in the app editor writes that code for you. Coworker access settings don't apply to apps. Apps can use Organization integrations, including in background jobs. A Private integration only works while the person who connected it is using the app, and never in background jobs. See [Working with code](https://docs.vybe.build/apps/working-with-code.md) and [Data](https://docs.vybe.build/apps/data.md). ## Security Vybe encrypts the credentials it stores, such as API keys, tokens, database URLs and the SSH private keys it generates. After you save a secret, Vybe never shows it again or sends it back to your browser. Database URLs are shown with the password hidden. See [Secrets and encryption](https://docs.vybe.build/security/secrets-and-encryption.md). > **[Integrations](https://docs.vybe.build/connections/integrations.md)** > > Connect apps from the catalog and use them in chat. > **[MCP servers](https://docs.vybe.build/connections/mcp-servers.md)** > > Add MCP servers from the catalog or by URL. > **[Custom APIs](https://docs.vybe.build/connections/custom-apis.md)** > > Connect any REST API with a key or token. > **[Databases](https://docs.vybe.build/connections/databases.md)** > > Connect your databases or create shared ones. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.