> ## 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. # MCP servers > Connect remote MCP servers from the built-in catalog or add your own by URL MCP (Model Context Protocol) servers let a service offer its tools directly to AI. Connect one, and your AI coworkers can call its tools the same way they use integrations. Use MCP when a service publishes an MCP server, or when you run your own. ## Connect a server from the catalog Vybe includes a catalog of remote MCP servers, such as GitHub, Linear, Sentry, Supabase, PostHog, Intercom, Mixpanel, Intuit QuickBooks, Square, Ramp, Klaviyo, Webflow and Zapier. Servers your organization added also appear in the list. **1. Open the server list** Go to **Connections** in the sidebar, open the **MCP** tab and click **Connect MCP**. The **Select MCP Server** dialog opens. **2. Pick a server** Search for the server and click it. **3. Sign in if needed** What happens next depends on how the server authorizes: * **Public**: Vybe connects right away. * **Token**: a **Connect to *name*** dialog asks for an **Auth token**. Paste it and click **Connect**. * **OAuth**: Vybe sends you to the service to sign in, then brings you back. From the **Connections** page, you land on **Settings → Data → MCP Servers**. For **Public** and **Token** servers, you'll see "Connected to *name*". **4. Review the settings** The account's settings dialog opens. Choose the **Visibility**, add a display name, and give coworkers access under **Agent access**. Connected servers appear on the **MCP** tab with a status: **Connected**, **Needs auth** or **Error**. ## Add your own server Add any remote MCP server that's reachable over HTTPS. **1. Open the form** Click **Connect MCP**, then **Create MCP Server**. **2. Fill in the details** | Field | What to enter | | - | - | | **Name** | A name for the server, such as "GitHub MCP". If the name doesn't contain "MCP", Vybe adds " MCP" to the end. | | **Server URL** | The server's Streamable HTTP or SSE endpoint, such as `https://mcp.example.com/sse`. It must use HTTPS. | | **Authorization** | **Public** (no sign-in), **Token** (a token sent as a bearer token on every request) or **OAuth** | | **Description (optional)** | What the server provides | **3. Create and connect** Click **Create MCP Server**. Vybe asks "Connect to *name*?". Click **Connect** to connect your account now, or **Skip** to do it later. > [!NOTE] > > For **OAuth**, the server must support OAuth discovery and dynamic client registration. Vybe checks this when you create the server. If it fails, you'll see "Failed to set up OAuth with the MCP server. If this persists, contact support." A server you add is listed for everyone in your organization. Each person connects their own account to it. You can't add the same URL with the same authorization type twice: Vybe replies "MCP server already exists". To remove a server you added, hover over it in the **Select MCP Server** list and click the trash icon. Only the person who added it, or an Owner or Admin, can delete it. Catalog servers can't be deleted. ## Visibility and coworker access MCP accounts work like integration accounts: * New accounts are **Private**. Switch to **Organization** to let everyone in your organization use the account. * AI coworkers have no access until you give it. Open the coworker's **Connections** section and use the **MCP** tab, use **Agent access** in the account's settings, or approve the coworker's request in chat. * Access levels are **Full access**, **Read only**, **Custom** (pick individual tools) or **Off**. **Read only** lets the coworker use only the tools the server marks as read-only. If a server doesn't mark any of its tools, **Read only** blocks all of them; use **Custom** to pick tools instead. See [How an AI coworker gets access](https://docs.vybe.build/connections/overview.md#how-an-ai-coworker-gets-access). ## Use MCP servers in chat Ask for what you need. If you have several MCP accounts, name the one you mean. > Use the Linear MCP to list issues assigned to me that are due this week. > Check Sentry for new errors in the checkout service since yesterday's deploy. The coworker's steps appear in its reply: | Step | What happened | | - | - | | "Listed MCP accounts" | It checked which MCP accounts it can see | | "Listed MCP tools" | It loaded the tools a server offers | | "Ran *tool*" | It called a tool. You can open the step to see its input and output. | | "Searched MCP servers for "*query*"" | It looked for a server you could connect | In the coworker's [activity history](https://docs.vybe.build/coworkers/usage-and-activity.md), each tool call appears as "Ran MCP tool". If the coworker needs a server you haven't connected, it shows a **Connect *name*** card. Connecting from the card gives that coworker access right away. If you already have a matching Private account, the card shows **Grant** instead. ## Disconnect an account Open **Connections**, go to the **MCP** tab, click the account and click **Disconnect *name***. Only the person who connected the account, or an Owner or Admin, can disconnect it. You can also manage accounts under **Settings → Data → MCP Servers**, which lists each account's URL, authorization type, who connected it and its visibility. ## Troubleshooting > **An account shows Needs auth or Error** > > The token or sign-in expired or was revoked, or the server can't be reached. Disconnect the account, connect the server again, then give your coworkers access to the new account. > **Failed to set up OAuth with the MCP server** > > The server doesn't support OAuth discovery or dynamic client registration. Check whether the server accepts a token instead, and add it with **Token** authorization. If the problem persists, contact [support@vybe.build](mailto:support@vybe.build). > **MCP server URL must use HTTPS** > > Vybe only connects to MCP servers over HTTPS. Use the server's `https://` endpoint. > **The coworker's tool calls keep failing** > > The coworker tells you which account is failing and what the error said. Check the account's token or permissions in the service, then reconnect if needed. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.