Skip to main content
Glama
ticksy-mcp

ticksy-mcp

by artkrsk

@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 reply

  • list_closed_tickets — most recently closed tickets

  • get_ticket — single ticket with full comment thread

  • get_ticket_comments — comments for a ticket without full ticket data

  • list_my_tickets — open tickets assigned to the authenticated agent

  • count_responses_needed — number of tickets awaiting a support response

  • count_my_responses — same, scoped to the authenticated agent

Write

  • reply_to_ticket — post a public reply (or staff-only with private: true)

  • add_ticket_note — post an internal note visible only to staff

  • close_ticket / reopen_ticket — change ticket status

  • mark_ticket_read / mark_ticket_unread — toggle read state

  • star_ticket / unstar_ticket — toggle star

  • create_customer — create a new customer account

Related MCP server: laravel-tasks

Setup

You need two environment variables:

  • TICKSY_DOMAIN — your subdomain (e.g. acme for acme.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-mcp

Add 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 build

Available Tools

16 tools
add_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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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_.

    Tool Count5/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers