mcp-otobo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTOBO_BASE_URL | Yes | Your Otobo instance URL (e.g. https://otobo.example.com) | |
| OTOBO_PASSWORD | Yes | Agent password | |
| OTOBO_USERNAME | Yes | Agent username for API access | |
| OTOBO_UNSAFE_SSL | No | Set to true to allow self-signed/internal SSL certificates | false |
| OTOBO_WEBSERVICE | No | Web service name configured in Otobo | GenericTicketConnectorREST |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ticketsA | Search Otobo tickets by various criteria (Queue, State, Priority, CustomerUser, Title, TicketNumber, date ranges, etc.) |
| get_ticketB | Get full ticket details by TicketID, including articles (communication history) and dynamic fields |
| create_ticketB | Create a new Otobo ticket with a first article (message) |
| update_ticketB | Update an existing Otobo ticket (change state, queue, priority, owner, etc.) and optionally add a new article |
| get_ticket_historyA | Get the full change history of a ticket (who changed what, when) |
| list_queuesA | List available Otobo queues by searching for tickets across all queues. Returns queue names found in the system. |
| list_statesA | List available Otobo ticket states by examining existing tickets. Returns state names found in the system. |
| list_prioritiesA | List available Otobo ticket priorities by examining existing tickets. Returns priority names found in the system. |
| close_ticketC | Close a ticket by setting its state to 'closed successful' and optionally adding a closing note |
| add_noteA | Add an internal note to a ticket without changing its state |
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 10 tools
Each tool targets a distinct operation on OTOBO tickets or metadata (priorities, queues, states), with no overlapping functionality. For example, add_note is clearly for internal notes vs. closing, while get_ticket_history is separate from get_ticket.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_ticket, list_priorities, close_ticket). No mixing of styles or ambiguous verbs.
10 tools is a well-scoped number for a ticket system, covering creation, retrieval, update, closing, history, and listing of metadata. Each tool earns its place without redundancy.
The set covers the main ticket lifecycle (create, read, update, close) and essential lookups (queues, states, priorities). Missing delete or archive operations, but those are often omitted in ticket systems for safety.