tickiti-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKITI_API_BASE | Yes | Your Tickiti install's public address, no trailing slash — e.g. https://support.example.com. The server appends /api/v1/…. | |
| TICKITI_API_TOKEN | Yes | The bearer token. Its abilities determine what the assistant can do. |
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 |
|---|---|
| create_ticketA | Create a support ticket. Provide originator_email_address and EXACTLY ONE of: subject+content, OR template_identifier+data, OR intervention+data+uid. Omit queue_name to use the Inbox; queue_name is not allowed with intervention. |
| respond_to_ticketA | Add a response to an existing ticket (reopens it if closed). Set is_internal=true for a staff-only note. |
| query_ticketsA | List tickets for a perspective (saved view). Specify perspective_id or perspective_name; defaults to the 'All' perspective. Pass a ticket number via search_object for a direct lookup. |
| list_perspectivesD | List saved perspectives (views) |
| list_watchlistsD | List watchlists |
| list_stock_responsesD | List stock (canned) responses |
| list_queuesD | List ticket queues |
| list_workflowB | List a plan-gated workflow collection: resolution-categories, interventions, or escalations. Returns 403 if the instance's plan does not include the feature. |
| run_reportA | Run a Tickiti analytics report (requires the reports plan + admin). 'meta' returns the filterable queues; the others accept date/queue filters via |
| list_endpointsA | Discover available Tickiti v1 endpoints. Optionally filter by family (one of: administration, idempotency_key, mail, reports, settings, supervisor, templates, tickets, workflow). Returns each endpoint's action key, required abilities, role, plan gates and path params — use these with tickiti_call. |
| tickiti_callA | Advanced escape hatch: invoke any Tickiti v1 endpoint not covered by a dedicated tool. Use list_endpoints first to find the family + action. payload becomes the JSON request body; for endpoints with path params (e.g. user, queue) include those keys in payload too. |
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 11 tools
Each tool targets a distinct operation: ticket creation, listing different resources, querying, responding, reporting, and an escape hatch. No overlapping purposes.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_ticket, list_endpoints, query_tickets). Even the generic 'tickiti_call' fits the pattern.
11 tools is well-scoped for a ticket management system, covering creation, listing, querying, responding, reporting, and advanced operations without unnecessary bloat.
The set covers the main ticket lifecycle (create, query, respond) and auxiliary lists. Minor gaps like explicit close or update are mitigated by the generic tickiti_call tool, so agents can work around them.