Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a
Zammad MCP is an MCP integration. Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a.
The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/zammad-v0.1.6/zammad-mcp.mcpb, version 0.1.6. Its declared MCP transport is stdio.
The package declares ZAMMAD_API_TOKEN (required): Set the ZAMMAD_API_TOKEN credential for the Zammad MCP server.; ZAMMAD_BASE_URL: Explicit full API base, e.g. https://support.example.com/api/v1. Overrides the instance URL above. Leave blank unless your instance serves the API somewhere non-standard.; ZAMMAD_URL (required): Root URL of your Zammad instance, e.g. https://support.example.com. The CLI appends /api/v1 itself. Without it the CLI points at a placeholder host that is not your instance.; ZAMMAD_MCP_HTTP_TOKEN: Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.; ZAMMAD_USER_AGENT: Overrides the User-Agent the CLI sends on Zammad requests. Leave blank to use the CLI's own built-in User-Agent.; PRINTING_PRESS_CLIENT_PROFILE: Binds this MCP server to one tenant-gated client profile. Leave blank to use the default client profile..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.1.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| ZAMMAD_API_TOKEN | Set the ZAMMAD_API_TOKEN credential for the Zammad MCP server. | Yes |
| ZAMMAD_BASE_URL | Explicit full API base, e.g. https://support.example.com/api/v1. Overrides the instance URL above. Leave blank unless your instance serves the API somewhere non-standard. | Optional |
| ZAMMAD_URL | Root URL of your Zammad instance, e.g. https://support.example.com. The CLI appends /api/v1 itself. Without it the CLI points at a placeholder host that is not your instance. | Yes |
| ZAMMAD_MCP_HTTP_TOKEN | Required only when running the MCP server with --transport http. Not needed for the default local stdio transport. | Optional |
| ZAMMAD_USER_AGENT | Overrides the User-Agent the CLI sends on Zammad requests. Leave blank to use the CLI's own built-in User-Agent. | Optional |
| PRINTING_PRESS_CLIENT_PROFILE | Binds this MCP server to one tenant-gated client profile. Leave blank to use the default client profile. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.