ticksy-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ticksy-mcp show open tickets awaiting a reply"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@artemsemkin/ticksy-mcp
MCP server for the Ticksy support ticket API. Gives AI agents full read and write access to your support tickets.
Tools
Read
list_open_tickets— open tickets with embedded comments; optionally filter to those awaiting a replylist_closed_tickets— most recently closed ticketsget_ticket— single ticket with full comment threadget_ticket_comments— comments for a ticket without full ticket datalist_my_tickets— open tickets assigned to the authenticated agentcount_responses_needed— number of tickets awaiting a support responsecount_my_responses— same, scoped to the authenticated agent
Write
reply_to_ticket— post a public reply (or staff-only withprivate: true)add_ticket_note— post an internal note visible only to staffclose_ticket/reopen_ticket— change ticket statusmark_ticket_read/mark_ticket_unread— toggle read statestar_ticket/unstar_ticket— toggle starcreate_customer— create a new customer account
Related MCP server: laravel-tasks
Setup
You need two environment variables:
TICKSY_DOMAIN— your subdomain (e.g.acmeforacme.ticksy.com)TICKSY_API_KEY— from your Ticksy profile page
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"ticksy": {
"command": "npx",
"args": ["-y", "@artemsemkin/ticksy-mcp"],
"env": {
"TICKSY_DOMAIN": "your-domain",
"TICKSY_API_KEY": "your-api-key"
}
}
}
}claude mcp add ticksy \
-e TICKSY_DOMAIN=your-domain \
-e TICKSY_API_KEY=your-api-key \
-- npx -y @artemsemkin/ticksy-mcpAdd to .vscode/mcp.json (VS Code) or .cursor/mcp.json (Cursor) in your project:
{
"servers": {
"ticksy": {
"command": "npx",
"args": ["-y", "@artemsemkin/ticksy-mcp"],
"env": {
"TICKSY_DOMAIN": "your-domain",
"TICKSY_API_KEY": "your-api-key"
}
}
}
}Build from source
git clone https://github.com/artkrsk/@artemsemkin/ticksy-mcp.git
cd @artemsemkin/ticksy-mcp
pnpm install
pnpm buildAvailable Tools
16 toolsadd_ticket_noteA
Post an internal note visible only to staff.
Inputs: comment (required), ticket_id (required).
close_ticketC
Close an open ticket.
Inputs: ticket_id (required).
count_my_responsesA
Count tickets assigned to you that await a response.
Inputs: no named parameters.
count_responses_neededA
Count open tickets awaiting a support response.
Inputs: no named parameters.
create_customerB
Create a new customer account.
Inputs: email (required), password (required), first_name (required).
get_ticketA
Get a single ticket with its full comment thread.
Inputs: ticket_id (required).
get_ticket_commentsA
Get comments for a ticket without full ticket data.
Inputs: ticket_id (required).
list_closed_ticketsA
List recently closed tickets (summary). Use get_ticket for full details.
Inputs: no named parameters.
list_my_ticketsA
List your assigned open tickets (summary). Use get_ticket for full details.
Inputs: no named parameters.
list_open_ticketsA
List open tickets (summary). Use get_ticket for full details.
Inputs: needs_response_only.
mark_ticket_readB
Mark a ticket as read.
Inputs: ticket_id (required).
mark_ticket_unreadC
Mark a ticket as unread.
Inputs: ticket_id (required).
reopen_ticketB
Reopen a closed ticket.
Inputs: ticket_id (required).
reply_to_ticketA
Post a public reply visible to the customer.
Inputs: comment (required), ticket_id (required), private.
star_ticketA
Star a ticket for follow-up.
Inputs: ticket_id (required).
unstar_ticketB
Remove star from a ticket.
Inputs: ticket_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Customer support for MCP servers: work your tickets from Claude or any MCP client. Service key auth.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Official MCP server for Agentwork — delegate tasks to AI agents with human-in-the-loop
Related MCP Servers
AlicenseBqualityBmaintenanceAn MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.11MIT- FlicenseNot gradedqualityDmaintenanceMCP server that connects to a Laravel Tasks API, enabling AI assistants to perform CRUD operations on tasks.-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for Zendesk Support that connects AI agents to 14 ticket tools including create, search, assign, close, comments, and metrics.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server exposing the internal Ticket API to MCP clients, built with FastMCP's OpenAPI integration.2-