How to Use the Unkey API Management MCP in CrewAI

Q: Can I manage key creation for different agents using Unkey API Management with CrewAI?

Yep. You use createapikey to provision unique keys for specific roles or agents. This means Agent A has access to its tools, and Agent B gets separate credentials.

Q: What data does Unkey API Management track regarding usage analytics with CrewAI?

The getverificationanalytics tool retrieves metrics on resource consumption. This is critical for the monitor agent to ensure no single specialized team member overwhelms a specific service.

Q: What if one agent needs its key revoked during an active CrewAI session?

You use revokeapikey to immediately shut down access. This prevents any compromised or unnecessary actions by that single agent, protecting the overall system.

Give specialized CrewAI agent teams secure access to APIs with Unkey API Management.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Unkey API Management MCP to CrewAI

Create your Vinkius account to connect Unkey API Management 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 Unkey API Management with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automated Key Provisioning

When a new task starts, the `create_api_key` tool lets you issue temporary credentials for the collaborating agents. If an agent needs a key update mid-task, `update_api_key` handles that without stopping the crew. This keeps your autonomous operations running smoothly by managing key lifecycles.

Monitor Resource Usage

The monitoring agent can use `get_verification_analytics` to track usage metrics across all team members. This tells you exactly which agents are hitting rate limits or using resources too aggressively. Understanding this prevents the entire crew from stalling out due to resource constraints.

Discover Available Services

Before any research begins, the specialized agent team needs a map. `list_apis` and `get_api_details` provide a full directory of available APIs in your Unkey project. This ensures that Agent A knows what tools it can use to research, before passing findings off to Agent B for analysis.

Setup guide

Set up Unkey API Management 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 Unkey API Management tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Unkey API Management 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="Unkey API Management Analyst",
        goal="Access and analyze Unkey API Management data via MCP.",
        backstory="Expert analyst with direct Unkey API Management access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Unkey API Management 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 Unkey. 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 Unkey API Management 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 Unkey API Management MCP in CrewAI

It provides a centralized credential source. By exposing tools like `verify_api_key`, every specialized agent can check credentials before making an external call, ensuring controlled access across the entire crew.

Yep. You use `create_api_key` to provision unique keys for specific roles or agents. This means Agent A has access to its tools, and Agent B gets separate credentials.

The `get_verification_analytics` tool retrieves metrics on resource consumption. This is critical for the monitor agent to ensure no single specialized team member overwhelms a specific service.

You use `revoke_api_key` to immediately shut down access. This prevents any compromised or unnecessary actions by that single agent, protecting the overall system.

It handles API keys and usage analytics. The centralized control provided by the MCP Server ensures all specialized agents operate under tightly managed and verifiable credentials.

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