Bring Api Gateway
to Cursor
Learn how to connect Tyk to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns Tyk into an in-editor superpower. Ask Cursor to generate code using live data from Tyk and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Tyk in Cursor
Tyk and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Tyk to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Fireflies.ai
12 toolsRecord, transcribe, and search across all your meetings with AI that captures every conversation and makes it instantly findable.
SmartChatAI
12 toolsManage AI bots, knowledge bases, and messaging on SmartChatAI with AI agents.
ANA (Movimentação de Dados)
18 toolsAccess and manage hydrometeorological data from the Brazilian National Water Agency (ANA) — query flow, rainfall, water quality, and cross-section series.
Precisely
10 toolsEquip your AI with precise location intelligence — geocode addresses, resolve property risks, calculate local taxes, and analyze demographics globally.