How to Use the Zammad MCP in Mastra AI

Q: How do I handle ticket creation with Zammad and Mastra AI?

You'll use the createticket tool. If the initial attempt fails, your workflow can automatically wait and retry creating the ticket until it succeeds or hits a predefined failure threshold.

Q: Can I list all Zammad groups using Mastra AI?

Yep. Just call listgroups. This is perfect for building an initial inventory check in your multi-step workflow before processing tickets.

Q: If I need to modify user details within Zammad and Mastra AI, which tools are best?

You'll use getuser first to fetch the existing data. Then, you call updateuser. This sequence allows your workflow to validate inputs before committing changes.

Q: Does this MCP Server support handling ticket details when interacting with Zammad and Mastra AI?

Absolutely. You can read the full state using getticket or check specific comments via listticketarticles. The reliability of these reads is key to your workflow.

Q: If I need to verify a user's deletion status using Zammad and Mastra AI, which data type should I focus on?

Focus on the user record itself. Use dataprivacydeleteuser to manage the underlying user account details.

Build resilient Zammad automation workflows with Mastra AI.

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 Mastra AI

Create your Vinkius account to connect Zammad to Mastra AI 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 Mastra AI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate User Lifecycle in Zammad via MCP Server

Need a user account created as part of an onboarding flow? Use `create_user` to provision the new identity within Zammad. Mastra AI can handle this step, and if it fails (say, due to existing credentials), your workflow engine retries with backoff. Want to clean up old accounts? The resilient pattern is using `data_privacy_delete_user`. This guarantees that even if the initial deletion attempt hits a snag, your complex Mastra AI process won't just crash.

Process Full Ticket Updates in Zammad with MCP Server

Updating tickets is rarely one step. You can build a conditional flow: first, use `get_ticket` to check the current status; if it's 'New', then call `update_ticket` to assign ownership and change priority. If you need more context, your workflow can follow up by calling `list_time_accountings`, ensuring every action taken on that Zammad ticket is logged properly.

Manage Content and Tags Across Zammad with MCP Server

Don't just write a ticket; enrich it. Your workflow can first use `list_all_tags` to fetch the required taxonomy, then apply them using `add_tag` on specific objects like tickets or users. This guarantees consistency across your system. You can also remove old tags from any object via `remove_tag`, managing Zammad data cleanup reliably.

Setup guide

Set up Zammad MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All Zammad tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "zammad-mcp-client",
  servers: {
    "zammad-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "Zammad Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to Zammad tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent Zammad transactions"
);
console.log(result.text);

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 Mastra AI

You'll use the `create_ticket` tool. If the initial attempt fails, your workflow can automatically wait and retry creating the ticket until it succeeds or hits a predefined failure threshold.

Yep. Just call `list_groups`. This is perfect for building an initial inventory check in your multi-step workflow before processing tickets.

You'll use `get_user` first to fetch the existing data. Then, you call `update_user`. This sequence allows your workflow to validate inputs before committing changes.

Absolutely. You can read the full state using `get_ticket` or check specific comments via `list_ticket_articles`. The reliability of these reads is key to your workflow.

Focus on the user record itself. Use `data_privacy_delete_user` to manage the underlying user account details.

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