Skip to main content
As LLMs become part of enterprise systems, teams need a way to govern them. Tyk provides two solutions. AI Studio manages the LLMs and AI applications you build. MCP Gateway governs AI agent access to MCP servers. It can also turn your own REST APIs into MCP servers.

​
AI Management Capabilities

Tyk provides two solutions for AI management:

​
AI Studio

Tyk AI Studio manages and deploys AI applications for platform teams. It provides:
  • LLM and model management to connect LLM vendors and models, commercial and in-house, and control which Teams and Users can access each one
  • Centralised governance with role-based access control and compliance tracking
  • Cost management through usage monitoring and budgeting tools
  • Credential management with unified access controls for AI vendor credentials
  • A curated AI service catalogue and Chat interface for building and running AI applications
Explore AI Studio

​
MCP Gateway

Tyk MCP Gateway puts Tyk’s API governance layer directly in front of remote MCP servers. This covers everything from GitHub Copilot and Slack to internal tools built by your own teams. It provides:
  • Authentication and key management with full OAuth 2.1 compliance, including Protected Resource Metadata discovery so MCP clients can self-configure
  • Access control at the individual tool, resource, and prompt level, so you can allowlist exactly which MCP primitives each agent can call
  • Traffic management including per-tool rate limiting, timeouts, circuit breakers, and request size limits
  • Unified credential management, so agents authenticate to Tyk once while Tyk handles per-vendor upstream credentials
  • Observability with per-tool analytics alongside the rest of your API traffic in the Tyk Dashboard
Direct connections from AI agents to remote MCP servers bypass every organisational control you have. Routing that traffic through Tyk makes it managed, auditable, and policy-enforced. Explore MCP Gateway

​
How they work together

Tyk’s two AI management capabilities are complementary:
  • AI Studio governs the LLM traffic and AI applications you build.
  • MCP Gateway governs AI agent traffic to MCP servers. These can be remote servers or servers that Tyk generates from your REST APIs.
Together, they cover AI traffic in both directions: the applications you create, and the tools your agents call.

​
Which one do I need?

  • Are you building and hosting your own AI applications or chat interfaces? Use AI Studio. It connects to LLM vendors, runs a Chat interface, and manages budgets. It also controls which Users and Teams can access which LLMs, Tools, and Data Sources.
  • Do you need to govern AI agent calls to MCP servers? Use MCP Gateway. It sits in front of any MCP server reachable over HTTP. That includes vendor servers such as Jira or Slack, and servers your own team runs. It adds authentication, per-tool access control, rate limits, and observability.
  • Do you want to expose your own Tyk-managed REST API as MCP tools? Use MCP Gateway with REST API to MCP. Tyk generates an MCP server from the API’s OpenAPI description, so you don’t build or host one.
  • Do you want an AI assistant to manage your Tyk deployment or search the Tyk docs? Connect it to the ready-to-use MCP servers for Tyk Dashboard and Tyk Docs.
These aren’t mutually exclusive. A common setup uses AI Studio to build and govern an internal AI application. Its agents then call out through MCP Gateway to remote MCP servers, and to your own APIs exposed with REST API to MCP.

​
Next steps

  1. Explore the AI Studio documentation
  2. Learn how MCP Gateway governs AI agent traffic to remote MCP servers
  3. Request a demo to see the platform in action