> ## Documentation Index > Fetch the complete documentation index at: https://slatehq.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # MCP servers > Connect remote MCP servers to Slate so Cowork can use their tools, with approval controls for write actions. MCP servers give [Cowork](/docs/agents/cowork/overview) new tools. Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside tools and data. Add a remote MCP server once, and everyone in your workspace can use its tools in Cowork. This page covers connecting other MCP servers to Slate. To use Slate from Claude instead, see [Claude MCP Connector](/docs/ai-tools/claude-mcp-connector). ## Why connect an MCP server to Slate? An MCP server adds tools Slate doesn't have built in, such as documentation search or an internal API. ## Prerequisites * The **Admin** role in your Slate workspace. Members can see connected servers but can't add them. * The URL of a public HTTPS MCP server that uses Streamable HTTP. Local (stdio) servers and multiple headers aren't supported. * The server's credentials, if it requires them ## Add a server ### Step 1: Enter the connection details 1. Open **Workspace settings → Integrations**. 2. On the **MCP servers** card, click **Add server**. 3. Enter a **Connection name** (up to 80 characters). 4. Enter the **MCP server URL**. 5. Choose an **Authentication** option: | Option | What you enter | | - | - | | **No authentication** (default) | Nothing else | | **Bearer token** | A **Bearer token** | | **Custom header** | A **Header name** (for example, `X-API-Key`) and a **Secret value** | | **Connect with OAuth** | Nothing. You approve access on the server's consent page. | Slate encrypts saved credentials and can't show them again. ### Step 2: Connect with a token, header, or no authentication 1. Click **Test connection**. Slate connects and discovers the server's tools. 2. On **Review MCP server**, check the "Connected to" host. 3. Under **What can Slate use this for?**, add up to six comma-separated capability hints, such as `official documentation, code samples`. 4. Optionally turn on **Run write tools without approval** (see [Write approval](#write-approval)). 5. Click **Connect server**. ### Step 2 (OAuth): Connect with OAuth 1. Optionally enter **Capabilities** as comma-separated hints. 2. Optionally turn on **Run write tools without approval**. 3. Click **Connect with OAuth**. The server's consent page opens in a new window. 4. Approve access. Slate discovers the server's tools after consent. The server appears on the **MCP servers** card with its tool count and "Writes need approval" or "Writes run without approval". ## How Cowork uses MCP tools Cowork uses the connection name and capability hints to decide when a server fits your request. Cowork works with up to 10 connected servers per workspace, starting with the earliest added. * Tools the server marks as read-only run automatically. * Write tools, and tools the server doesn't classify, need approval before they run. ### Approve a write tool When Cowork wants to run a write tool, it shows a card titled **Run** followed by the tool name: "Slate wants to make this change on your behalf — it needs your OK first." 1. Expand **Review details** to see the exact inputs. 2. Click **Approve** to run the tool, or **Deny** to decline. Admins also see **Run future write tools from this server without approval**. Turn it on before you click **Approve** to stop future prompts for that server. ### Write approval **Run write tools without approval** lets Slate run write and unclassified tools from a server without asking. Only Admins can change it. With this setting on, Cowork can change data in the connected tool without a confirmation step. Turn it on only for servers you trust. Replacing a server's authentication, or reconnecting OAuth, turns approval back on. ## Manage a server Open the **⋮** menu on a server's row: * **Edit settings** — change the name, **Capabilities**, authentication, or write approval, then click **Save changes**. * **Test connection** — recheck the server and refresh its tool count. * **Disconnect** — remove the server. | Action | Who can do it | | - | - | | Add a server | Admins | | Edit settings | Admins and the person who added the server | | Replace authentication | The person who added the server. Admins can also reconnect OAuth servers. | | Change write approval | Admins | | Disconnect | The person who added the server | ## Reconnect a server An OAuth server shows **Reconnect needed** when its access expires or is revoked. Cowork can't use it until it's reconnected. 1. Click **Reconnect** on the server's row. The dialog shows "OAuth access expired or was revoked. Reconnect to use this server again." 2. Click **Save changes**. The server's consent page opens in a new window. 3. Approve access. Slate confirms: "OAuth reconnected. Write approval is required again." A server with a token or header shows **Needs attention** when its connection isn't valid. To fix it: 1. In the **⋮** menu, choose **Edit settings**. 2. Turn on **Replace authentication** and re-enter the exact server URL and new credentials. 3. Click **Save changes**. ## Troubleshooting | Issue | Cause | Solution | | - | - | - | | **Test connection** fails | The URL isn't a public HTTPS Streamable HTTP endpoint, or the credentials are wrong | Check the URL and credentials | | "Add up to 6 capabilities" or "Each capability must be 40 characters or fewer" | Too many hints, or a hint is too long | Use up to six hints of 40 characters or fewer | | "MCP server URL cannot change during reconnect" | You entered a different URL while replacing authentication | Add the new URL as a separate server | | Cowork doesn't use a server | The server isn't **Connected**, its hints don't match, or 10 servers were added first | Reconnect it, improve its hints, or disconnect unused servers | ## What's next * [Cowork](/docs/agents/cowork/overview) — ask Slate to research, write, and run tools * [Claude MCP Connector](/docs/ai-tools/claude-mcp-connector) — use Slate from Claude This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.