How to Use the 42Crunch MCP in CrewAI

Q: How do I give different CrewAI agents access to different 42Crunch tools?

Use the toolfilter option when you configure the MCPServerHTTP source for your agent. This lets you grant the triggeraudit tool to your 'Auditor' agent while only giving the listapis tool to your 'Monitor' agent, enforcing role separation.

Q: What's the simplest way to connect 42Crunch to a CrewAI agent?

Just pass your Vinkius MCP URL into the mcps array when you define an Agent. CrewAI will connect, discover all available 42Crunch tools, and attach them to the agent automatically. It's the fastest way to get started.

Q: Can one CrewAI agent get a list of APIs from 42Crunch and have another agent scan them?

That's exactly the model. An 'Explorer' agent runs listapis and passes the resulting list of IDs to a 'Scanner' agent as part of a sequential task. The agents hand off work to each other, just like a real team.

Deploy a crew of AI agents to continuously monitor and secure your APIs with 42Crunch and CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect 42Crunch MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble an API Security Crew

CrewAI is about specialized agents working together. You can create a 'Monitor' agent whose only job is to run `list_apis` every hour. When it detects a new or changed API, it passes the API ID to a different agent on the crew. An 'Auditor' agent receives that ID. Its sole purpose is to execute the `trigger_audit` tool. Once the audit is running, it delegates the task of checking the results to a 'Reporter' agent. This division of labor makes your automation clear and manageable.

Autonomous Audit and Response

This is how you build a system that runs itself. The 'Reporter' agent gets an audit ID, waits, and then calls `get_audit_report`. It's programmed to look for specific, critical vulnerabilities in the report data. If it finds something serious, it doesn't just send an alert. It delegates to an 'Action' agent. This agent can use other tools to file a P0 ticket, lock a deployment pipeline, or page an engineer. This entire MCP-driven workflow runs with zero human intervention.

Hierarchical API Management

You can set up a 'Manager' agent to oversee your entire API security posture. This agent uses `list_collections` to get a high-level view. It then assigns specific maintenance tasks to subordinate agents in the crew. For instance, the manager can tell a 'Janitor' agent to run `delete_api` on all APIs that haven't been scanned in 90 days. Or it can task an 'Importer' agent with using `import_api` to add all new specs from a specific repository. This is how you automate security governance at scale.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Yes. Assign one CrewAI agent to monitor for new API specs, another to run `trigger_audit` via 42Crunch, and a third to analyze the `get_audit_report` results. The crew works together to create a continuous, autonomous monitoring loop.

Use the `tool_filter` option when you configure the `MCPServerHTTP` source for your agent. This lets you grant the `trigger_audit` tool to your 'Auditor' agent while only giving the `list_apis` tool to your 'Monitor' agent, enforcing role separation.

Just pass your Vinkius MCP URL into the `mcps` array when you define an Agent. CrewAI will connect, discover all available 42Crunch tools, and attach them to the agent automatically. It's the fastest way to get started.

That's exactly the model. An 'Explorer' agent runs `list_apis` and passes the resulting list of IDs to a 'Scanner' agent as part of a sequential task. The agents hand off work to each other, just like a real team.

Your API definitions are streamed to a sandboxed Vinkius execution environment for each tool call. The environment is torn down after the 42Crunch tool, like `trigger_audit`, finishes its job. No data is ever written to disk or stored, ensuring your sensitive API information remains confidential.

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