How to Use the Tyk MCP in CrewAI

Q: How do I set up an API definition with Tyk and CrewAI?

You use createapidefinition via the MCP Server. This step defines the resource that all specialized agents in your crew will interact with.

Q: Does CrewAI need to manage credentials when interacting with Tyk?

Yes, you'll use createkey or updatekey to provide current credentials. The MCP Server handles the secure generation and update of these required keys.

Q: What if an agent in CrewAI needs a new access policy from Tyk?

You run the createpolicy tool. This allows you to programmatically add role-based restrictions, ensuring that Agent A can't accidentally use resources meant only for Agent B.

Q: Can I list all API definitions using Tyk and CrewAI?

You call listapis. This function gives the entire team a manifest of every defined resource, letting you ensure no part of your operation is missed.

Run dedicated operational teams that manage APIs using the CrewAI framework.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Tyk MCP to CrewAI

Create your Vinkius account to connect Tyk to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Tyk with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Define core API definitions for CrewAI

The `create_api_definition` tool lets your crew define a new API resource. This is where you tell the team exactly what data they can access and how they should interact with it. This foundational step ensures that specialized agents—like the Researcher or Analyzer—are working off of clear, defined service boundaries.

Manage credentials for agent teams

When you need a new credential set for an agent (say, the Executor), use `create_key`. You can also create organization-level keys using `create_org_key`. This granular control over access helps your multi-agent system isolate roles and ensure agents only have the minimum permissions necessary to complete their task.

Control team access with policy management

Use `create_policy` to establish strict rules for how a specialized agent can interact with an API. You'll also use `delete_policy` when a role changes or becomes obsolete. This mechanism is crucial for controlling the blast radius if one of your autonomous agents starts behaving unexpectedly.

Setup guide

Set up Tyk MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Tyk tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Tyk Analyst",
    goal="Access and analyze Tyk data via MCP.",
    backstory="Expert analyst with direct Tyk access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Tyk transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Tyk Analyst",
        goal="Access and analyze Tyk data via MCP.",
        backstory="Expert analyst with direct Tyk access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Tyk transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Tyk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Tyk now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Tyk MCP in CrewAI

You use `create_api_definition` via the MCP Server. This step defines the resource that all specialized agents in your crew will interact with.

Yes, you'll use `create_key` or `update_key` to provide current credentials. The MCP Server handles the secure generation and update of these required keys.

You run the `create_policy` tool. This allows you to programmatically add role-based restrictions, ensuring that Agent A can't accidentally use resources meant only for Agent B.

You call `list_apis`. This function gives the entire team a manifest of every defined resource, letting you ensure no part of your operation is missed.

The server manages API definitions and credentials. The most sensitive piece of information handled here that impacts security is the `API key`, which must be managed with strict role boundaries.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript