Schema | ticksy-mcp

ticksy-mcp

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

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/artkrsk/ticksy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server