# MCP Servers
URL: /mcp-servers
Type: howto
Description: Connect external MCP servers so Stylo can discover and use their tools in workflows and AI conversations.
Keywords: mcp, model context protocol, servers, tools
MCP Servers let you connect Stylo to an external Model Context Protocol server and use that server's tools inside Stylo. This is useful when you already have MCP-compatible tools and want Stylo to call them without building a custom native integration first.

{/* TODO(docs): Screenshot of the MCP Servers page showing server status, tool count, and the Add Server button. Tracked in public/images/README.md. */}

What MCP Servers are for [#what-mcp-servers-are-for]

Use an MCP server when you want Stylo to work with tools that live outside Stylo, such as internal support systems, custom data services, or operational actions exposed through an MCP endpoint.

In the current product, MCP servers are described as available for:

* Workflows
* AI conversations

Before you start [#before-you-start]

MCP Servers are gated by plan. In the current product, the MCP Servers area is shown as a Professional feature, and your workspace can only create up to the number of MCP servers allowed by your plan.

Before you add a server, make sure you have:

* The server URL
* Any required request headers
* A clear understanding of which tools the server exposes
* A safe test environment if those tools can make external changes

Add an MCP server [#add-an-mcp-server]

1. Go to **Integrations**.
2. Open the **MCP Servers** tab.
3. Click **Add Server**.
4. Enter a **Name**.
5. Enter the server **URL**.
6. Add an optional **Description**.
7. Add any required **Headers** as key-value pairs.
8. Click **Create Server**.

Stylo then opens the server detail page, where you can test the connection and discover tools.

Test the connection [#test-the-connection]

After creating a server, open its detail page and click **Test Connection**.

Stylo tracks the connection status as:

* **Connected** when the server can be reached successfully
* **Disconnected** before a successful connection has been recorded
* **Error** when the last connection or tool refresh failed

If a connection attempt fails, the detail page shows the latest error message so you can correct the URL, headers, or server availability.

Refresh tools [#refresh-tools]

Stylo does not assume the tool list automatically. Use **Refresh Tools** on the detail page to discover the tools exposed by the server.

After a successful refresh, Stylo stores:

* The number of discovered tools
* The latest refresh time
* The discovered tool definitions

The **Discovered Tools** section then shows each tool's:

* Name
* Description, when provided by the server
* Parameter count

{/* TODO(docs): GIF of testing an MCP server connection and refreshing discovered tools. Tracked in public/images/README.md. */}

How discovered tools are used [#how-discovered-tools-are-used]

Once Stylo has successfully discovered tools from a connected server, those tools can be turned into Stylo tools and workflow blocks.

In practice, this means:

* A healthy MCP server can contribute tools for AI use
* Refreshed tools can appear as dynamic integration blocks in workflows
* Servers in an error state are not eligible for workflow blocks

If you change the tools on the remote MCP server, refresh the server in Stylo so the stored tool list stays current.

Edit an MCP server [#edit-an-mcp-server]

You can edit the same fields that are exposed in the current form:

* Name
* URL
* Description
* Headers

Use this when:

* The server endpoint changes
* Authentication headers rotate
* You want a clearer name or description for the team

Delete an MCP server [#delete-an-mcp-server]

You can delete an MCP server from the list page or the detail page.

Deleting a server:

* Cannot be undone
* Removes it from Stylo's MCP server list
* Stops Stylo from using that server as an MCP source

Limits and safety [#limits-and-safety]

* MCP servers can expose real actions, not just lookups. Test them before using them in production workflows.
* If a server is unreachable or returns errors, Stylo records the failure and marks the connection status as **Error**.
* If your workspace reaches its MCP server limit, Stylo blocks creation of additional servers.
* Headers you enter are kept in Stylo's secret storage, not retained in the form after you save.

{/* TODO(docs): the create/edit forms don't expose the timeout or enabled fields yet, though the detail screen shows a timeout value. Document guidance for those controls once the surface is confirmed. */}

Recommended rollout pattern [#recommended-rollout-pattern]

For most teams, the safest rollout is:

1. Add one MCP server for a narrow use case.
2. Test the connection.
3. Refresh tools and review what is exposed.
4. Verify the tools in a controlled workflow or internal AI use case.
5. Add broader or more sensitive servers only after the first setup is stable.

Related [#related]

* Start with [Integrations](/integrations) for the broader integrations model
* Continue to [Response Workflows](/response-workflows) if you want to use discovered tools in automations