Zammad MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAMMAD_URL | Yes | Base URL of the Zammad instance, without /api/v1 | |
| MCP_HTTP_PORT | No | Listen port in http mode | 8214 |
| ZAMMAD_HTTP_TOKEN | No | Personal API token used in community mode | |
| ZAMMAD_TIMEOUT_SECONDS | No | Total timeout for one Zammad request | 30 |
| ZAMMAD_CONNECT_TIMEOUT_SECONDS | No | Connect timeout for one Zammad request | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meA | Return the Zammad user the current token belongs to (id, login, name, email, roles). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another tool. Its purpose is clearly stated as returning the current Zammad user.
The single tool name follows a clear snake_case verb_object convention (get_me). No inconsistency can exist with only one tool.
A Zammad server with only one trivial identity tool is an extreme mismatch for the platform's scope. Zammad is a full helpdesk system requiring at least ticket, user, and organization operations.
The surface is severely incomplete for a Zammad integration. There are no tools for tickets, users, organizations, groups, or any CRUD/lifecycle operations, leaving agents unable to perform meaningful helpdesk tasks.