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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/domnussbaum/otobo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server