How to Use the ContextQA MCP in CrewAI

Q: Can a CrewAI agent autonomously trigger a ContextQA run?

Yes, you can assign triggerrun to a CrewAI action agent to launch ContextQA test pipelines based on monitoring events.

Q: How do I restrict which ContextQA MCP Server tools my CrewAI agents can use?

Use MCPServerHTTP with toolfilter to expose only specific tools like listapitests to your researcher CrewAI agents.

Q: How does this MCP Server secure my ContextQA API schemas and test cases in CrewAI?

All REST configurations and test case trees fetched via listapitests and listcases are processed in-memory inside your CrewAI runtime. Vinkius uses zero-trust sandboxes to guarantee that your proprietary ContextQA testing schemas never leak outside your active CrewAI session.

Run autonomous QA agent crews to monitor, heal, and trigger ContextQA tests with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ContextQA MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent ContextQA Test Auditing in CrewAI

`list_api_tests` gives your CrewAI agent team the MCP tools they need to audit your ContextQA endpoints. A CrewAI researcher agent pulls the ContextQA test configs while an analyst agent compares them against active API schemas. The CrewAI crew uses `list_cases` to map out the routing limits of your ContextQA test trees. This allows the CrewAI agents to identify gaps in your ContextQA test coverage without any manual intervention.

Monitor Healing Runs with Specialized Crews

`get_execution` checks the live healing state of active ContextQA runs while a specialized CrewAI monitoring agent watches for failures. If a ContextQA run stalls, a CrewAI moderator agent takes over to diagnose the root cause. By calling `list_executions`, the CrewAI crew tracks global ContextQA run chunks to build a complete timeline of the execution. This shared memory keeps all agents on the CrewAI team updated on the ContextQA test status.

Autonomous Multi-Project ContextQA Runs

`list_projects` identifies bounded ContextQA test environments so your CrewAI crew can run validations across multiple targets simultaneously. Each CrewAI agent handles a specific ContextQA project to avoid resource conflicts. When a project is ready, a CrewAI action agent uses `trigger_run` to launch the ContextQA pipeline jobs. The entire process runs autonomously from start to finish within your ContextQA-focused CrewAI crew.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Yes, you can assign `trigger_run` to a CrewAI action agent to launch ContextQA test pipelines based on monitoring events.

CrewAI agents use shared memory to pass ContextQA states retrieved by `get_execution` and `list_executions` back and forth.

Use `MCPServerHTTP` with `tool_filter` to expose only specific tools like `list_api_tests` to your researcher CrewAI agents.

Yes, the ContextQA server handles concurrent requests from multiple CrewAI agents running in your crew.

All REST configurations and test case trees fetched via `list_api_tests` and `list_cases` are processed in-memory inside your CrewAI runtime. Vinkius uses zero-trust sandboxes to guarantee that your proprietary ContextQA testing schemas never leak outside your active CrewAI session.

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