Stateless remote MCP server for Zammad — full ticket operations, an intelligent search layer and OAuth 2.1, running on Node.js or Cloudflare Workers
Stateless remote MCP server for Zammad — full ticket operations, an intelligent search layer and OAuth 2.1, running on Node.js or Cloudflare Workers from one codebase. That is what the zammad mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Everything lives in zammad-remote-mcp. The source keeps the runtimes apart, but there is a single version and a single publish.
Configuration is passed through the environment: PUBLIC_URL, ZAMMAD_URL, ZAMMAD_OAUTH_CLIENT_ID, ZAMMAD_OAUTH_CLIENT_SECRET, OAUTH_STATE_SECRET, ZAMMAD_API_TOKEN, YOUR_ZAMMAD_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as zammad-remote-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Zammad's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"remote-1": {
"command": "npx",
"args": ["-y", "zammad-remote-mcp"],
"env": {
"PUBLIC_URL": "your-value",
"ZAMMAD_URL": "your-value",
"ZAMMAD_OAUTH_CLIENT_ID": "your-value",
"ZAMMAD_OAUTH_CLIENT_SECRET": "your-value",
"OAUTH_STATE_SECRET": "your-value",
"ZAMMAD_API_TOKEN": "your-value",
"YOUR_ZAMMAD_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| ZAMMAD_URL | Endpoint or connection string the server talks to. | Yes |
| ZAMMAD_OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| ZAMMAD_OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| OAUTH_STATE_SECRET | Credential the server authenticates with. | Yes |
| ZAMMAD_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_ZAMMAD_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.