Compatible with every major AI agent and IDE
What is the Tyk MCP Server?
Connect your Tyk instance to any AI agent to streamline your API management and gateway operations through conversation.
What you can do
- Key Management — Create, retrieve, update, and delete API keys (Session Objects) directly in the Tyk Gateway.
- Security Policies — Define and manage security policies to control access rights and rate limits across your API ecosystem.
- API Definitions — List all active API definitions from your Dashboard and create new ones using the Tyk Classic format.
- Gateway Control — Trigger hot reloads to force the Gateway to refresh its configuration and apply changes instantly.
- Granular Inspection — Fetch detailed metadata for specific keys and policies to audit access and performance metrics.
How it works
- Subscribe to this server
- Provide your Tyk URL and Gateway Secret (or Dashboard Token)
- Start managing your API infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Automate gateway reloads and policy updates without leaving the terminal or chat interface.
- Backend Developers — Quickly generate API keys and check definition statuses during the development lifecycle.
- Security Teams — Audit existing policies and keys to ensure compliance with organizational access standards.
Built-in capabilities (12)
Requires TYK_DASHBOARD_TOKEN. Create a new API definition
Requires TYK_GATEWAY_SECRET. Create a new API key (Session Object)
Requires TYK_ADMIN_SECRET. Create an organization key
Requires TYK_GATEWAY_SECRET. Create a new security policy
Requires TYK_GATEWAY_SECRET. Delete an API key
Requires TYK_GATEWAY_SECRET. Delete a policy
Requires TYK_GATEWAY_SECRET. Get details for a specific API key
Requires TYK_GATEWAY_SECRET. Get details of a single policy
Requires TYK_GATEWAY_SECRET. Force Gateway hot reload
Requires TYK_DASHBOARD_TOKEN. List all API definitions
Requires TYK_GATEWAY_SECRET. Update an existing API key
Requires TYK_GATEWAY_SECRET. Update an existing policy
Why VS Code Copilot?
GitHub Copilot Agent mode brings Tyk data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Tyk in VS Code Copilot
Tyk and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Tyk to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Tyk in VS Code Copilot
The Tyk MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Tyk for VS Code Copilot
Every tool call from VS Code Copilot to the Tyk MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I apply changes to my Tyk Gateway after updating a policy?
You can use the hot_reload tool. This forces the Tyk Gateway to reload its configuration and API definitions, ensuring all updates are live without a full restart.
Can I list all my existing API definitions from the Dashboard?
Yes! Use the list_apis tool. It returns a paginated list of all API definitions. You can also filter by name using the optional search string.
Is it possible to retrieve the details of a specific API key?
Absolutely. Use the get_key tool with the specific Key ID. The agent will return the session object, including access rights and rate limit configurations.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Upzelo
10 toolsReduce subscription churn with personalized retention offers that intercept cancellations and win back customers at the exit point.

Tesla Fleet API
8 toolsPhysical actuator proxy mapping explicitly native commands evaluating telemetry tracking active Tesla vehicles cleanly.

Telegram Bot API
10 toolsConnect your AI natively to Telegram. Read user messages, administrate chats, send push notifications, and automate media distribution directly from the prompt.

Freshdesk
10 toolsResolve customer tickets faster with omnichannel helpdesk tools, smart automation, and self-service portals your users will love.
