How to Use the AlisQI MCP in CrewAI

Q: How can I assign different AlisQI tools to different agents in my CrewAI team?

When defining an Agent in CrewAI, you can use the toolfilter argument in the MCPServerHTTP configuration. This lets you write a function that determines exactly which AlisQI tools from this MCP Server that particular agent is allowed to use.

Assemble an autonomous crew of AI agents to monitor and manage your AlisQI data 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 AlisQI MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Deploy a Quality Audit Crew

This MCP Server gives your CrewAI agents the tools to perform complex quality audits by assigning different roles to each agent. For example, a 'Scout' agent's only job is to use `list_analysis_sets` to find relevant quality control plans. It then passes the list of sets to an 'Auditor' agent. The Auditor's job is to execute `list_results` for each set to gather all the data. Finally, an 'Analyst' agent takes this raw data, looks for patterns or outliers, and compiles a summary report. Each agent does one thing well.

Automated Incident Response Team

The tools in this server let you build an autonomous crew that responds to quality issues without human intervention. A 'Monitor' agent can run in a loop, periodically calling `list_results` with a filter for 'failed' tests. As soon as it finds one, it triggers the next agent in the sequence. An 'Investigator' agent takes the failed result ID and uses `get_result_details` and `get_result_attachments` to pull all available context. It then hands off a complete dossier to a 'Notifier' agent, which formats and sends an alert to the right people. The whole process is autonomous.

A CrewAI Crew for System Administration

Use the tools in this server to create a CrewAI team that automates the administration of your QMS integration. Assign a 'SysAdmin' agent to periodically run `get_api_info` to check the API status and `list_fields` to check for schema changes. If it detects an unexpected change or an API outage, it can delegate a task to a 'Communicator' agent. That agent's role is to post a status update to a specific channel or open a support ticket. This divides the labor, making the whole system more robust.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

When defining an Agent in CrewAI, you can use the `tool_filter` argument in the `MCPServerHTTP` configuration. This lets you write a function that determines exactly which AlisQI tools from this MCP Server that particular agent is allowed to use.

Yes, that's a perfect use case. You'd set up a 'Monitor' agent in a sequential crew that uses the `list_results` tool on a schedule. When it finds new results that match your criteria, it passes them to the next agent in the crew for processing.

A three-agent hierarchical crew works well. Have a manager agent oversee the process. A 'Data-Gatherer' agent uses `list_results` to pull the data. A 'Data-Analyst' agent then processes the data from the shared context to find insights. The manager coordinates their work.

Yes. CrewAI's MCP integration lets you filter tools when you define the server for an agent. This way, you can create specialized agents, like one that can only read data (`list_results`) and another that can only write data (`store_results`).

Your AlisQI quality management data, including results and attachments, is handled securely. Each tool call from your CrewAI agent goes to an isolated, single-use server instance on Vinkius that is destroyed after the call completes. Vinkius never stores your data.

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