4,000+ servers built on vurb.ts
Vinkius

Zammad MCP Server for CrewAIGive CrewAI instant access to 41 tools to Add Tag, Create Ticket, Create Ticket Article, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Zammad MCP Server for CrewAI is a standout in the Communication Messaging category — giving your AI agent 41 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Zammad Specialist",
    goal="Help users interact with Zammad effectively",
    backstory=(
        "You are an expert at leveraging Zammad 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 Zammad "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 41 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Zammad
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 Zammad MCP Server

Connect your Zammad helpdesk to any AI agent to streamline your customer support and user management through natural conversation.

When paired with CrewAI, Zammad becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zammad 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

  • Ticket Management — List, retrieve, and create tickets to stay on top of customer requests using list_tickets and get_ticket.
  • User & Organization Control — Search, create, and update user profiles and organizational data with tools like search_users and list_organizations.
  • Group & Role Insights — List and search through system groups and roles to understand permissions and assignments.
  • Data Privacy — Securely handle user deletions via specialized data privacy tasks using data_privacy_delete_user.

The Zammad MCP Server exposes 41 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 41 Zammad tools available for CrewAI

When CrewAI connects to Zammad through Vinkius, your AI agent gets direct access to every tool listed below — spanning ticket-management, customer-service, user-management, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add tag on Zammad

Add a tag to an object

create

Create ticket on Zammad

Create a new Zammad ticket

create

Create ticket article on Zammad

Create a new article on a ticket

create

Create user on Zammad

Create a new Zammad user

data

Data privacy delete user on Zammad

Delete a user via Data Privacy task (Recommended over direct delete)

delete

Delete ticket on Zammad

Delete a Zammad ticket

delete

Delete user on Zammad

Delete a Zammad user

get

Get group on Zammad

Get details for a specific Zammad group

get

Get links on Zammad

Get links for a specific object

get

Get me on Zammad

Get current Zammad user details

get

Get organization on Zammad

Get details for a specific Zammad organization

get

Get shared draft on Zammad

Get shared draft for a ticket

get

Get ticket on Zammad

Get details for a specific Zammad ticket

get

Get ticket article on Zammad

Get details for a specific ticket article

get

Get user on Zammad

Get details for a specific Zammad user

list

List all tags on Zammad

List all tags in the system (Admin)

list

List calendars on Zammad

List calendars

list

List checklist items on Zammad

List checklist items

list

List checklist templates on Zammad

List checklist templates

list

List checklists on Zammad

List checklists

list

List groups on Zammad

List all Zammad groups

list

List mentions on Zammad

List mentions

list

List organizations on Zammad

List all Zammad organizations

list

List roles on Zammad

List all Zammad roles

list

List slas on Zammad

List SLAs

list

List tags for object on Zammad

List tags for a specific object (e.g., Ticket)

list

List ticket articles on Zammad

List articles for a specific ticket

list

List ticket priorities on Zammad

List ticket priorities

list

List ticket states on Zammad

List ticket states

list

List tickets on Zammad

List Zammad tickets

list

List time accountings on Zammad

List time accountings for a ticket

list

List users on Zammad

List all Zammad users

remove

Remove tag on Zammad

Remove a tag from an object

search

Search groups on Zammad

Search for groups in Zammad

search

Search organizations on Zammad

Search for organizations in Zammad

search

Search roles on Zammad

Search for roles in Zammad

search

Search tickets on Zammad

Search for tickets in Zammad

search

Search users on Zammad

Search for users in Zammad

summarize

Summarize ticket on Zammad

Trigger async generation of a ticket summary

update

Update ticket on Zammad

Update an existing Zammad ticket

update

Update user on Zammad

Update an existing Zammad user

Connect Zammad to CrewAI via MCP

Follow these steps to wire Zammad into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 41 tools from Zammad

Why Use CrewAI with the Zammad MCP Server

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

01

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

02

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

03

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

04

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

Zammad + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Example Prompts for Zammad in CrewAI

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

01

"List all active tickets in Zammad."

02

"Search for a user with the email 'customer@example.com'."

03

"Get the details for ticket ID 42."

Troubleshooting Zammad MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Zammad + CrewAI FAQ

Common questions about integrating Zammad MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →