4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Zammad MCP Server

Bring Ticket Management
to Cursor

Learn how to connect Zammad to Cursor and start using 41 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add TagCreate TicketCreate Ticket ArticleCreate UserData Privacy Delete UserDelete TicketDelete UserGet GroupGet LinksGet MeGet OrganizationGet Shared DraftGet TicketGet Ticket ArticleGet UserList All TagsList CalendarsList Checklist ItemsList Checklist TemplatesList ChecklistsList GroupsList MentionsList OrganizationsList RolesList SlasList Tags For ObjectList Ticket ArticlesList Ticket PrioritiesList Ticket StatesList TicketsList Time AccountingsList UsersRemove TagSearch GroupsSearch OrganizationsSearch RolesSearch TicketsSearch UsersSummarize TicketUpdate TicketUpdate User

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Zammad

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

How it works

  1. Subscribe to this server
  2. Enter your Zammad URL and Personal Access Token
  3. 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_tag

Add a tag to an object

create_ticket

Create a new Zammad ticket

create_ticket_article

Create a new article on a ticket

create_user

Create a new Zammad user

data_privacy_delete_user

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

delete_ticket

Delete a Zammad ticket

delete_user

Delete a Zammad user

get_group

Get details for a specific Zammad group

get_links

Get links for a specific object

get_me

Get current Zammad user details

get_organization

Get details for a specific Zammad organization

get_shared_draft

Get shared draft for a ticket

get_ticket

Get details for a specific Zammad ticket

get_ticket_article

Get details for a specific ticket article

get_user

Get details for a specific Zammad user

list_all_tags

List all tags in the system (Admin)

list_calendars

List calendars

list_checklist_items

List checklist items

list_checklist_templates

List checklist templates

list_checklists

List checklists

list_groups

List all Zammad groups

list_mentions

List mentions

list_organizations

List all Zammad organizations

list_roles

List all Zammad roles

list_slas

List SLAs

list_tags_for_object

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

list_ticket_articles

List articles for a specific ticket

list_ticket_priorities

List ticket priorities

list_ticket_states

List ticket states

list_tickets

List Zammad tickets

list_time_accountings

List time accountings for a ticket

list_users

List all Zammad users

remove_tag

Remove a tag from an object

search_groups

Search for groups in Zammad

search_organizations

Search for organizations in Zammad

search_roles

Search for roles in Zammad

search_tickets

Search for tickets in Zammad

search_users

Search for users in Zammad

summarize_ticket

Trigger async generation of a ticket summary

update_ticket

Update an existing Zammad ticket

update_user

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

See it in action

Zammad in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →