How do I find my AlisQI Bearer Token?

Log in to AlisQI, navigate to **Menu** > **Management** > **Integration Hub**. You can generate and manage your API tokens there. Each token inherits the permissions of the associated user account.

Is the data model the same for everyone?

No, AlisQI uses a dynamic, user-defined data model. This means field names and analysis sets are specific to your company's configuration. Use the `list_analysis_sets` tool to discover your unique structure.

Can I attach files to quality results via the agent?

Currently, the agent can retrieve metadata for existing attachments using the `get_result_attachments` tool. For uploading new files, we recommend using the AlisQI web interface or specific integration endpoints.

AlisQI MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: AlisQI
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to AlisQI through Vinkius, pass the Edge URL in the `mcps` parameter and every AlisQI tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="AlisQI Specialist",
    goal="Help users interact with AlisQI effectively",
    backstory=(
        "You are an expert at leveraging AlisQI tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in AlisQI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About AlisQI MCP Server

Connect your AlisQI instance to your AI agent to unlock professional quality management (QMS) orchestration. From auditing quality results and managing analysis sets to retrieving technical metadata for fields and monitoring workflow webhooks, your agent handles your quality operations through natural conversation.

When paired with CrewAI, AlisQI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AlisQI tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Results Orchestration — List, retrieve, and store quality results for any of your custom analysis sets
Schema Discovery — List and audit analysis sets and their field definitions to understand your dynamic data model
Document Oversight — Retrieve technical metadata for result attachments and monitor your quality documentation
Workflow Monitoring — List active webhooks to ensure your quality event triggers (like non-conformities) are operational
QMS Insights — Quickly identify quality trends or audit recent analysis entries directly from your chat interface

The AlisQI MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect AlisQI to CrewAI via MCP

Follow these steps to integrate the AlisQI MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from AlisQI

Why Use CrewAI with the AlisQI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AlisQI through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

AlisQI + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AlisQI MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AlisQI for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries AlisQI, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AlisQI tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries AlisQI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AlisQI MCP Tools for CrewAI (10)

These 10 tools become available when you connect AlisQI to CrewAI via MCP:

get_analysis_set_details

Get set metadata

get_api_info

Check API status

get_result_attachments

List document attachments

get_result_details

Get specific result

list_active_webhooks

List active triggers

list_analysis_sets

List analysis sets

list_choice_lists

List selection menus

list_fields

List dynamic fields

list_results

Supports filtering. List quality results

store_results

Create or update results

Example Prompts for AlisQI in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AlisQI immediately.

"List all analysis sets available in my AlisQI instance."

"Show the last 5 quality results for 'Raw Material Inspection'."

"Check if there are any active webhooks for non-conformities."

Troubleshooting AlisQI MCP Server with CrewAI

Common issues when connecting AlisQI to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

AlisQI + CrewAI FAQ

Common questions about integrating AlisQI MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.