Zammad MCP for AI. Manage users, tickets, and groups from your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Zammad MCP automates your entire helpdesk workflow, letting you manage tickets, users, and organizational data directly from any AI client.
Need to update a user profile or close out an account? You can do it without leaving your current chat window.
What your AI can do
Add tag
Applies a specific label to any object within Zammad.
Create ticket article
Adds a structured comment or piece of information to an existing ticket thread.
Create ticket
Generates an entirely new support ticket record in the system.
Create new issues, fetch details on existing tickets, update status records, and summarize the entire ticket history.
Find specific users by email or ID, create new user profiles, modify user details, or securely delete accounts following data privacy rules.
List and search through groups, organizations, and roles to understand who has access to what parts of the system.
Get details for any object—from a specific ticket article to an entire organization record—to verify context before making changes.
Add or remove tags on tickets and other objects, helping sort data and route issues automatically.
Ask an AI about this
Waiting for input…
Zammad MCP with 41 Tools
Use these tools to manage every aspect of your helpdesk: creating tickets, modifying users, updating groups, and auditing system data.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Zammad on VinkiusAdd Tag
Applies a specific label to any object within Zammad.
Create Ticket Article
Adds a structured comment or piece of information to an existing ticket thread.
Create Ticket
Generates an entirely new support ticket record in the system.
Create User
Sets up and generates a brand new user profile in Zammad.
Data Privacy Delete User
Deletes a user account using the official data privacy procedure, which is safer...
Delete Ticket
Permanently removes an entire support ticket record from Zammad.
Delete User
Deletes a user account in the system.
Get Group
Pulls all the specific details for one chosen Zammad group.
Get Links
Retrieves related links or associated data points for a given object ID.
Get Me
Displays the current user's own details within Zammad.
Get Organization
Fetches all the detailed information for a specific organizational unit.
Get Shared Draft
Retrieves a shared draft that is ready to be attached to an existing ticket.
Get Ticket Article
Retrieves the content and context for a single article within a ticket thread.
Get Ticket
Fetches the full details and status of one specific support ticket.
Get User
Pulls all specific details for one chosen Zammad user account.
List All Tags
Shows every available tag category in the entire system (Admin function).
List Calendars
Retrieves a list of all active calendars within Zammad.
List Checklist Items
Displays the items available for use in checklist templates.
List Checklist Templates
Gets a list of all pre-built checklist templates used by users.
List Checklists
Retrieves an overview of the available checklists in Zammad.
List Groups
Lists every group defined within the system.
List Mentions
Fetches a list of all mentions made across Zammad objects.
List Organizations
Retrieves a complete list of all organizational units in the system.
List Roles
Displays every defined role and its permissions within Zammad.
List Slas
Lists all Service Level Agreements (SLAs) configured for tickets.
List Tags For Object
Shows which tags are applicable to a specific type of object, like a ticket or user.
List Ticket Articles
Gets all the articles that belong to one specific support ticket.
List Ticket Priorities
Displays the available priority levels for tickets (e.g., High, Medium).
List Ticket States
Lists every possible status a ticket can be in (Open, Closed, Pending).
List Tickets
Retrieves a list of tickets based on general criteria.
List Time Accountings
Fetches records showing how much time was spent working on a specific ticket.
List Users
Gets a complete list of all user accounts registered in Zammad.
Remove Tag
Removes an existing tag from a designated object.
Search Groups
Searches for groups by name or description within Zammad.
Search Organizations
Searches for organizational units by keyword or criteria.
Search Roles
Searches the list of roles to find specific permissions.
Search Tickets
Searches for tickets using keywords, IDs, or status filters.
Search Users
Finds users by name, email, or other identifying details.
Summarize Ticket
Triggers a background process to generate a concise summary of the ticket's...
Update Ticket
Modifies key details on an existing support ticket, like status or assignment.
Update User
Changes specific data points for an existing user profile in Zammad.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Zammad integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Zammad, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Zammad. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 41 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Juggling Support Data Across Too Many Tabs
Right now, updating a user's profile or closing out an account means opening the ticket dashboard, pulling the user ID, switching over to the admin panel to check group memberships, and then manually applying tags. It’s a painful cycle of copying and pasting data between siloed screens.
With this MCP, you just talk to your agent. You tell it the goal—'Deactivate account X because they moved departments.' The agent handles finding the user (`get_user`), updating their status (`update_user`), removing old tags (`remove_tag`), and generating a final ticket record for tracking.
Using Zammad to Manage User Accounts
You manually search the user list, then open individual profiles one by one just to check if they belong to the 'Premium' organization. This takes minutes and introduces human error.
Now you ask your agent: 'Show me all users assigned to the Premium group.' The system searches across groups (`search_groups`) and lists only those people. It’s instant, reliable data that saves time.
What your AI can actually do with this
Working with customer service means jumping between multiple tabs—the ticket system, the user directory, the billing portal. This MCP connects Zammad so you can handle all those tasks through natural conversation. Your agent doesn't just read data; it performs actions: creating new tickets and updating associated users or adding tags to an organization record.
For example, if a customer calls about a billing issue, your agent can instantly find the user's profile, check their organizational assignment, create a detailed ticket, and even add specific internal tags, all in one go. Because every action is logged and visible through Vinkius AI Analytics, you always know exactly what data flowed and which tools were called, keeping an auditable trail of everything that happens.
This means complex workflows—like migrating user accounts or setting up new organizational structures—are managed with total visibility.
019e3910-3587-722e-a17c-ff970d95b827 
Here's how it actually works
The bottom line is that you manage complex helpdesk operations using simple chat commands instead of clicking through multiple web pages.
Connect your Zammad credentials (URL and Personal Access Token) to the Vinkius platform.
Select this MCP in your preferred AI client—Claude, Cursor, or any compatible agent.
Ask your agent a command like, 'Find user X, create a ticket about their login issue, and tag it as Billing.' The agent executes all steps.
Who is this actually for?
The Tier 1 Support Rep who gets frustrated having to copy user IDs from one dashboard and paste them into another. The System Admin who needs an auditable way to audit permissions across dozens of groups. DevOps engineers running automated compliance checks.
Uses the agent to quickly pull up user history, list active tickets, and manage ticket priorities without switching tabs.
Manages group roles, searches for users by email, and updates organization settings directly from the chat interface.
Integrates helpdesk data into automated reporting pipelines, ensuring that user creation or deletion events trigger downstream actions in other systems.
What Changes When You Connect
Instead of opening 5 tabs to check a user's profile, ticket history, and group membership, you ask your agent for everything in one prompt. It handles the data retrieval instantly.
You don't have to manually copy IDs or tags across systems. Your agent manages the full lifecycle—from calling get_user to executing add_tag on a related ticket.
The ability to build automations that cross multiple platforms is massive. You can combine this Zammad MCP with, say, an HR system MCP and a billing MCP to fully process an account migration.
You'll never worry about data integrity or visibility again. Vinkius ensures every tool call produces a cryptographically signed audit trail, so you always know who did what and when.
If your workflow is complex, the agent handles it cleanly. You can chain calls like search_users followed by create_ticket, then update_user—all in one continuous interaction.
See it in action
Onboarding a New Client
A new client signs up. Instead of manually creating the user, updating their organizational assignment, and logging the initial request, you prompt your agent: 'Create user John Doe in the Acme Corp organization and open a welcome ticket.' The agent handles create_user, updates the necessary details using get_organization data, and runs create_ticket.
Handling Data Purges
A user requests account deletion. Instead of running a simple delete command that might violate compliance rules, you ask your agent to execute the secure process: 'Delete this user's data per policy.' The agent uses data_privacy_delete_user and confirms the action.
Escalating Complex Issues
A ticket requires more context. You ask your agent to find all related details: 'What are the links, roles, and groups for ticket ID 42?' The agent uses get_ticket first, then calls get_links, followed by list_roles and get_group data points.
Auditing Permissions
An internal audit is required. You ask your agent to list all groups and check their roles: 'List all security groups and show which roles are assigned.' The agent uses list_groups, then calls search_roles for each one.
The honest tradeoffs
Sequential, Manual Data Entry
You read a user's email from Ticket A, open the User Directory to find their ID, then switch to the Group Management screen to see what groups they belong to.
Use your agent and prompt it: 'Find all details for the user associated with this ticket.' The agent handles get_user and cross-references group data in one call.
Incomplete User Updates
You only remember to update the name on the profile but forget to change their primary organization or add a required tag.
Tell your agent the full scope: 'Update user Jane Doe's role, set her organization to Global, and remove the old billing tag.' The agent calls update_user, then get_organization, followed by remove_tag.
Using Generic Search Only
Searching for a ticket using only keywords in the main search bar, which might miss related metadata or articles.
Ask your agent to search specifically: 'Find all tickets matching these criteria and list their associated articles.' The agent handles search_tickets then calls list_ticket_articles.
When It Fits, When It Doesn't
Use this MCP if you need to manage the full lifecycle of data—meaning, you're not just reading information. You must be able to create tickets, update users, or modify organizational metadata via a conversational prompt. Don't use it if your only goal is simple reporting; for pure read-only dashboards, you might find a dedicated read-API tool better. However, if the data points are spread across multiple entities (e.g., 'What was the user assigned to this ticket doing last month?'), then this MCP and its ability to chain together get_user, list_tickets, and list_time_accountings is absolutely necessary.
Questions you might have
How do I use `list_tickets` with Zammad? +
You ask your agent to list tickets and can specify criteria like status or date range. It pulls a clean summary, so you don't have to sift through the main dashboard view.
Can I use `data_privacy_delete_user` instead of just deleting a user? +
Yes. The data_privacy_delete_user tool follows Zammad’s recommended protocol for deletion, ensuring that the account is scrubbed correctly and auditable.
What's the difference between `create_ticket` and `update_ticket`? +
create_ticket starts a brand new issue from scratch. Use update_ticket when the ticket already exists, but you need to change its status or add more details.
How does Zammad handle organization data with this MCP? +
You can search for organizations (search_organizations) and fetch full details using get_organization, letting your agent confirm if a user belongs to the right structure before making any changes.
What information can I retrieve about a specific user using `get_user`? +
The tool returns comprehensive details, including the user's assigned organization, contact info, and group memberships. This lets your agent pull all necessary context in one call, so you don't have to jump between different sections of Zammad.
How do I add new notes or updates using `create_ticket_article`? +
You send the article content and target ticket ID to generate a new message thread. This is perfect for adding internal investigation notes or requesting follow-up details without changing the core status of the original request.
What does `list_roles` allow me to manage within Zammad? +
list_roles shows all predefined user roles and their associated permissions. This helps system admins understand who can do what, letting your agent verify if a user has the right access before attempting an action.
How does `add_tag` help categorize tickets or users? +
You apply specific keywords (tags) to objects like tickets and users for easy filtering. This lets your agent automatically sort incoming requests, ensuring they go straight to the right team without manual effort.
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.
We've already built the connector for Zammad. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 41 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.