> ## Documentation Index
> Fetch the complete documentation index at: https://tyk.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Tyk MCP Servers

> The MCP servers Tyk offers: Tyk Docs MCP, Tyk Dashboard MCP, and REST API to MCP in Tyk Gateway. Use MCP Gateway to govern any MCP server.

Tyk offers three MCP servers for AI assistants and agents:

* **Tyk Docs MCP** lets an AI assistant search and read the Tyk documentation.
* **Tyk Dashboard MCP** lets an AI assistant query and manage your Tyk deployment in plain language.
* **REST API to MCP** turns your own Tyk-managed REST APIs into MCP tools, inside Tyk Gateway.

To govern MCP servers, use [MCP Gateway](https://tyk.io/docs/ai-management/mcp-gateway/overview.md). It sits in front of any MCP server reachable over HTTP, whether a vendor runs it or your own team does.

## Compare Tyk MCP Servers

| MCP server | Use it to | Where it runs |
| :- | :- | :- |
| [Tyk Docs MCP](https://tyk.io/docs/ai-management/mcps/tyk-docs-mcp.md) | Search and read the Tyk docs | Hosted by Tyk at `https://tyk.io/docs/mcp` |
| [Tyk Dashboard MCP](https://tyk.io/docs/ai-management/mcps/dashboard-api-to-mcp.md) | Query and manage your Tyk deployment | On your machine, through `npx` |
| [REST API to MCP](https://tyk.io/docs/ai-management/mcps/api-to-mcp.md) | Expose your Tyk OAS APIs as MCP tools, with Tyk policies applied | In Tyk Gateway |

## Tyk Docs MCP

Tyk Docs MCP connects an AI assistant to the live Tyk documentation. The assistant can then answer questions about Tyk from current content, with links to the relevant docs sections. Tyk hosts the server, so you only add its URL to your assistant:

```bash theme={null}
npx add-mcp https://tyk.io/docs/mcp
```

See [Tyk Docs MCP](https://tyk.io/docs/ai-management/mcps/tyk-docs-mcp.md) for manual configuration and supported assistants.

## Tyk Dashboard MCP

Tyk Dashboard MCP exposes the Tyk Dashboard API to an AI assistant. You can ask questions such as "Which APIs are active?" or "What is the rate limit on API X?". It includes the Tyk Dashboard OpenAPI specification, so you don't need to supply one. The tool is open source: see the [tyk-dashboard-mcp repository](https://github.com/TykTechnologies/tyk-dashboard-mcp).

See [Tyk Dashboard MCP](https://tyk.io/docs/ai-management/mcps/dashboard-api-to-mcp.md) for the configuration and examples.

## REST API to MCP

REST API to MCP generates an MCP server from a Tyk OAS API that is already in Tyk. Tyk Gateway turns each REST operation you select into an MCP tool, so you don't build or host a separate MCP server. The generated server is an MCP proxy, so the same MCP Gateway policies, rate limits, and analytics apply to it.

Use this option to make your production APIs available to agents under central governance.

See [REST API to MCP](https://tyk.io/docs/ai-management/mcps/api-to-mcp.md) for how it works and its current limitations.

## Govern MCP Servers With MCP Gateway

[MCP Gateway](https://tyk.io/docs/ai-management/mcp-gateway/overview.md) adds authentication, per-tool access control, rate limits, and observability to MCP traffic. It supports the MCP `2025-11-25` specification from Tyk Gateway v5.13. To manage MCP proxies in Kubernetes, see [Manage MCP Servers with Tyk Operator](https://tyk.io/docs/product-stack/tyk-operator/mcp-proxy.md).

## Publish MCP Servers to Developers

The Tyk Developer Portal can publish MCP proxies as products for API consumers:

* [View MCP Documentation in the Developer Portal](https://tyk.io/docs/portal/mcp-documentation.md): how MCP products and their tools appear in the Live Portal.
* [Test MCP Tools with the Embedded MCP Inspector](https://tyk.io/docs/portal/mcp-inspector-playground.md): call a product's tools before writing agent code.
* [Access Protected MCP Proxies with OAuth 2.1](https://tyk.io/docs/portal/mcp-oauth-access.md): get credentials for OAuth 2.1-protected MCP proxies.