How to Use the Context7 MCP in CrewAI

Equip your CrewAI specialist agents with real-time library documentation via Context7.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Context7 MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Divide and conquer documentation lookup in CrewAI

In a CrewAI setup, you don't want one agent doing everything. You can assign a Researcher agent to locate the correct library path using `resolve_library`, while a separate Coder agent uses those paths to fetch examples. By passing the Vinkius URL in the `mcps` array, both agents share access to the MCP Server tools. The Researcher hands off the deterministic path to the Coder agent, who then runs `query_docs` to write clean, tested code.

Autonomous code monitoring with MCP Server tools

Set up a CrewAI supervisor agent to watch your repository for deprecated imports. When it detects an old library, it triggers a sub-agent to query `resolve_library` for the latest stable release. The sub-agent pulls the updated migration guides using `query_docs` and writes a pull request. This entire upgrade cycle runs autonomously in the background without developers needing to manually read changelogs.

Selective tool exposure for CrewAI teams

You might not want your junior agents querying raw documentation endpoints directly. CrewAI allows you to use `MCPServerHTTP` from `crewai.mcp` with a custom `tool_filter` to restrict access. You can expose `resolve_library` to your planning agents while keeping `query_docs` locked down for execution agents. This strict boundary keeps your agent communication clear and prevents token waste.

Setup guide

Set up Context7 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 Context7 tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

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

The easiest way is passing your Vinkius HTTP URL directly into the agent's `mcps` parameter during initialization.

Yes. CrewAI's shared memory allows the researcher to save the resolved path from `resolve_library` so the coder can use it in `query_docs`.

Instead of scraping entire websites, Context7 returns targeted markdown blocks. This keeps the context window clean for all agents in your CrewAI team.

Absolutely. Agent A can resolve the library path, and Agent B can sequentially query the docs to perform the required code updates.

All queries are processed inside a zero-trust, ephemeral V8 sandbox. Vinkius never logs or retains the library names or code queries generated by your CrewAI agents.

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