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 VS Code Copilot?
GitHub Copilot Agent mode brings Zammad data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 41 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Zammad in VS Code Copilot
Zammad and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Zammad to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
EBI InterPro
16 toolsClassify protein sequences into families, predict functional domains, and explore evolutionary relationships across species.

Toast
10 toolsManage restaurant orders, menus, employees, labor, tables, and payments for your Toast POS through natural conversation.

Chroma (Vector DB)
7 toolsManage vector embeddings via Chroma — list collections, query embeddings, and audit document counts directly from any AI agent.

Amazon Redshift
7 toolsEquip your AI to directly query, analyze, and manage your petabyte-scale data warehouse via the serverless AWS Redshift Data API.
