MCP server for searching and retrieving OTOBO tickets
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"otobo-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OTOBO MCP Server An [MCP](https://modelcontextprotocol.io) server for searching and retrieving tickets from [OTOBO](https://otobo.io) via the Generic Interface REST API. ## Prerequisites - Python 3.10+ - An OTOBO instance with the Generic Interface enabled - [uv](https://docs.astral.sh/uv/) package manager ### OTOBO web service setup In **Admin > Web Services**, create or edit a web service with these operations: | Operation | Route | Method | |------------------------|-----------------|--------| | Ticket::TicketSearch | /TicketSearch | POST | | Ticket::TicketGet | /TicketGet | POST | POST is required for both — GET cannot handle the nested search parameters. ## Quickstart ```bash git clone https://github.com/youruser/otobo-mcp-server.git cd otobo-mcp-server # Create environment and install dependencies uv venv source .venv/bin/activate uv sync ``` Run the server: ```bash # STDIO (default) uv run otobo_mcp_server.py # SSE uv run otobo_mcp_server.py -t sse -p 8080 # Streamable HTTP uv run otobo_mcp_server.py -t streamable-http -p 8080 ``` ## Configuration All configuration is through environment variables: | Variable | Required | Default | Description | |--------------------|----------|------------------------------|------------------------------------| | `OTOBO_HOST` | yes | | Base URL, e.g. `https://otobo.example.com` | | `OTOBO_USER` | yes | | Agent username | | `OTOBO_PASSWORD` | yes | | Agent password | | `OTOBO_WEBSERVICE` | no | `GenericTicketConnectorREST` | Web service name in OTOBO admin | | `OTOBO_SSL_VERIFY` | no | `true` | SSL certificate verification | | `OTOBO_TIMEOUT` | no | `30` | HTTP timeout in seconds …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.