How to Use the Zammad MCP in Cursor

Q: How do I reference Zammad tickets in my Cursor project?

You use the agent mode to call getticket right into your file. The generated code uses live data, so you get real ticket IDs and statuses without needing mock stubs.

Q: Can Cursor help me manage Zammad users?

Yep. You can write functions that call getuser or even createuser. Since it's a code editor, you get the syntax correct immediately for your application.

Q: If I need to search Zammad groups in Cursor, how do I do it?

Just activate Agent mode and ask it to use searchgroups. The live data gets written into your code structure, letting you build features around group membership.

Q: Does the Zammad integration in Cursor handle complex ticket updates?

It does. You can update tickets using updateticket and then reference that updated record's details in your subsequent code blocks, ensuring data consistency.

Q: What kind of data does the Zammad MCP Server touch regarding privacy?

This server handles user-level data via getuser calls and ticket content. The specific type of data touched is structured text/records, which you can manage using listtimeaccountings.

Write code that uses live Zammad API data directly with Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Zammad MCP to Cursor

Create your Vinkius account to connect Zammad to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Zammad with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Injecting current ticket status into code.

Writing a script that needs to know if an issue is open? Use `get_ticket` and the `list_ticket_states` tool to fetch real-time Zammad status. The agent generates working code that uses this live API response, not fake data. You can also pull articles using `get_ticket_article`. This means your application code gets context from a specific conversation thread when it's running.

Managing users and groups in scripts.

Need to write logic around user permissions? Call `list_users` or use `get_user` to pull current Zammad user details right into your function. The code will reference the actual IDs, making it immediately usable. For complex organization checks, run `search_groups` and inject the results directly. This handles multi-level access checks in your application logic.

Automating tag creation for records.

When you write a script that needs to categorize tickets, use `add_tag`. The agent figures out which tags are needed and injects the correct calls using `list_all_tags` data. You can also run code to remove old context by calling `remove_tag`, ensuring your application only processes records with up-to-date metadata.

Setup guide

Set up Zammad MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Zammad MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Zammad transactions." If the MCP tools are loaded correctly, Cursor will call the Zammad tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "zammad-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Zammad now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Zammad MCP in Cursor

You use the agent mode to call `get_ticket` right into your file. The generated code uses live data, so you get real ticket IDs and statuses without needing mock stubs.

Yep. You can write functions that call `get_user` or even `create_user`. Since it's a code editor, you get the syntax correct immediately for your application.

Just activate Agent mode and ask it to use `search_groups`. The live data gets written into your code structure, letting you build features around group membership.

It does. You can update tickets using `update_ticket` and then reference that updated record's details in your subsequent code blocks, ensuring data consistency.

This server handles user-level data via `get_user` calls and ticket content. The specific type of data touched is structured text/records, which you can manage using `list_time_accountings`.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript