ticksy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKSY_DOMAIN | Yes | Your subdomain (e.g. acme for acme.ticksy.com) | |
| TICKSY_API_KEY | Yes | Your Ticksy API key from your profile page |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_open_ticketsA | List open tickets (summary). Use get_ticket for full details. |
| list_closed_ticketsA | List recently closed tickets (summary). Use get_ticket for full details. |
| get_ticketA | Get a single ticket with its full comment thread. |
| get_ticket_commentsA | Get comments for a ticket without full ticket data. |
| list_my_ticketsA | List your assigned open tickets (summary). Use get_ticket for full details. |
| count_responses_neededA | Count open tickets awaiting a support response. |
| count_my_responsesA | Count tickets assigned to you that await a response. |
| reply_to_ticketA | Post a public reply visible to the customer. |
| add_ticket_noteA | Post an internal note visible only to staff. |
| close_ticketC | Close an open ticket. |
| reopen_ticketB | Reopen a closed ticket. |
| mark_ticket_readB | Mark a ticket as read. |
| mark_ticket_unreadC | Mark a ticket as unread. |
| star_ticketA | Star a ticket for follow-up. |
| unstar_ticketB | Remove star from a ticket. |
| create_customerB | Create a new customer account. |
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 16 tools
Each tool targets a distinct action or data view. Even similar tools like count_responses_needed and count_my_responses are clearly differentiated by scope. Pairs like reply_to_ticket vs add_ticket_note and mark/unmark actions are unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs are clear and actions are predictable, such as count_, list_, get_, create_, and action pairs like close_/reopen_ and mark_/unmark_.
16 tools is appropriate for a ticketing system covering creation, listing, details, and common actions. Each tool serves a distinct purpose and the count is well-scoped without unnecessary redundancy.
The tool set is severely incomplete for a ticketing system. Crucially, there is no tool to create a ticket, and no update or delete ticket functionality. This will prevent agents from performing basic lifecycle operations, leading to failures.