OTRS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTRS_DEBU G | No | Logging de debug | false |
| OTRS_DB_PATH | No | Caminho do SQLite | /data/otrs-mcp.db |
| OTRS_TIMEOUT | No | Timeout HTT P em segundos | 30 |
| OTRS_BASE_URL | Yes | URL completa do webservice OTRS (obrigatorio) | |
| OTRS_MCP_HOST | No | Host do MCP server (modo http) | 0.0.0.0 |
| OTRS_MCP_PORT | No | Porta do MCP server (modo http) | 8001 |
| OTRS_PASSWORD | Yes | Senha do OTRS (obrigatorio) | |
| OTRS_USERNAME | Yes | Usuario do OTRS (obrigatorio) | |
| OTRS_ADMIN_USER | No | Usuario admin padrao (criado na 1a execucao) | admin |
| OTRS_JWT_SECRET | No | Secret para assinatura JWT. Se nao definido, um segredo aleatorio e gerado | |
| OTRS_VERIFY_SSL | No | Verificar certifcados SSL | true |
| OTRS_CORS_ORIGINS | No | Origens permitidas CORS | http://localhost:5173,... |
| OTRS_DEFAULT_TYPE | No | Tipo padrao | Unclassified |
| OTRS_WEB_BASE_URL | No | URL da interface web OTRS (derivaado) | |
| OTRS_ACTIVITY_FILE | No | Arquivo de log de atividade MCP | /data/activity.json |
| OTRS_MCP_TRANSPORT | No | Transporte: stdio ou http | stdio |
| OTRS_ADMIN_PASSWORD | Yes | Senha do admin padrao (criado na 1a execucao). Obrigatorio definir! | |
| OTRS_DEFAU LT_QUEUE | No | Fila padrao | Raw |
| OTRS_DEFAU LT_STATE | No | Estado padrao | new |
| OTRS_DEFAULT_PRIORITY | No | Prioridade padrao | 3 normal |
| OTRS_JWT_EXPIRE_MINUTES | No | Tempo de vida do JWT (8 horas) | 480 |
| OTRS_ACTIVITY_MAX_EVENTS | No | Maximo de eventos no JSON | 1000 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_ticketC | Create a new ticket in OTRS |
| get_ticketB | Get ticket details from OTRS |
| search_ticketsC | Search for tickets in OTRS |
| update_ticketC | Update an existing ticket in OTRS |
| get_ticket_historyC | Get ticket history from OTRS |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| search_tickets_resource | Retorna tickets recentes com links para a interface web. |
TDQS
Scored across 5 tools
Each tool targets a distinct operation on tickets: create, retrieve individual details, search, update, and retrieve history. There is no meaningful overlap between get_ticket and get_ticket_history because one returns current state and the other returns the audit trail.
All tools follow a consistent verb_noun pattern with snake_case: create_ticket, get_ticket, search_tickets, update_ticket, get_ticket_history. The only minor variation is the plural 'tickets' in search_tickets, which is natural and does not break the pattern.
Five tools is well-scoped for a ticket management server. Each tool represents a core operation without unnecessary redundancy, making the set easy to navigate.
The tool surface covers the essential ticket lifecycle: creation, retrieval, search, update, and history lookup. For OTRS, this is a complete and practical set with no obvious dead ends.