Compatible with every major AI agent and IDE
What is the Zammad MCP Server?
Connect your Zammad helpdesk to any AI agent to streamline your customer support and user management through natural conversation.
What you can do
- Ticket Management — List, retrieve, and create tickets to stay on top of customer requests using
list_ticketsandget_ticket. - User & Organization Control — Search, create, and update user profiles and organizational data with tools like
search_usersandlist_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.
How it works
- Subscribe to this server
- Enter your Zammad URL and Personal Access Token
- Start managing your helpdesk from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Support Leads — quickly get ticket statuses and user history without switching tabs.
- System Admins — manage users, groups, and organizations directly from the terminal or AI interface.
- DevOps Engineers — integrate helpdesk data into automated workflows and reporting.
Built-in capabilities (41)
Add a tag to an object
Create a new Zammad ticket
Create a new article on a ticket
Create a new Zammad user
Delete a user via Data Privacy task (Recommended over direct delete)
Delete a Zammad ticket
Delete a Zammad user
Get details for a specific Zammad group
Get links for a specific object
Get current Zammad user details
Get details for a specific Zammad organization
Get shared draft for a ticket
Get details for a specific Zammad ticket
Get details for a specific ticket article
Get details for a specific Zammad user
List all tags in the system (Admin)
List calendars
List checklist items
List checklist templates
List checklists
List all Zammad groups
List mentions
List all Zammad organizations
List all Zammad roles
List SLAs
List tags for a specific object (e.g., Ticket)
List articles for a specific ticket
List ticket priorities
List ticket states
List Zammad tickets
List time accountings for a ticket
List all Zammad users
Remove a tag from an object
Search for groups in Zammad
Search for organizations in Zammad
Search for roles in Zammad
Search for tickets in Zammad
Search for users in Zammad
Trigger async generation of a ticket summary
Update an existing Zammad ticket
Update an existing Zammad user
Why Cursor?
Cursor's Agent mode turns Zammad into an in-editor superpower. Ask Cursor to generate code using live data from Zammad and it fetches, processes, and writes. all in a single agentic loop. 41 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Zammad in Cursor
Zammad and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Zammad to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Zammad in Cursor
The Zammad 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. All 41 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Zammad for Cursor
Every tool call from Cursor to the Zammad MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for specific users or organizations within Zammad?
Yes! You can use the search_users and search_organizations tools to find specific records using search queries directly from your AI agent.
How do I safely delete a user according to data privacy standards?
It is recommended to use the data_privacy_delete_user tool. This initiates a Data Privacy task in Zammad, which is the preferred method over direct deletion for compliance.
Can I view my own Zammad profile details?
Yes, the get_me tool allows you to retrieve the profile details of the currently authenticated user associated with your access token.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Conductor (Netflix OSS)
49 toolsAutomate workflow orchestration via Netflix Conductor — manage workflow and task definitions, and start executions directly from any AI agent.

All Digital Rewards
10 toolsIncentive and reward orchestration — manage participants, points, and catalogs via AI.

Strava Social
10 toolsExplore Strava activities feed, kudos, comments, clubs, and discover new segments.

Hexometer
11 toolsAutomate website monitoring via Hexometer — monitor uptime, performance, and health directly from any AI agent.
