create_ticketLABSCO SUMMARY
Triage and answer support tickets without opening the helpdesk.
The whole agent loop is here — find the ticket, read the thread, reply or leave a note, then set priority, state, tags and owner — so a morning triage pass happens in one conversation instead of thirty clicks.
What it is
A remote server for the Ticketdesk AI helpdesk that opens the ticket queue, the full conversation on any ticket, and the actions an agent takes on one.
What you get
- The ticket list, filtered by state, priority, assigned agent or tags
- One ticket in full, with its activity history
- Replies sent to the customer, and internal notes that stay internal
- Assignment to an agent, and moving a ticket to a different inbox
- Priority, state and tags set from the conversation
- New tickets raised with subject, requester details, priority and tags
Requirements
A Ticketdesk AI account and an API key generated from Settings > API Keys. The key travels in the endpoint URL, so treat the connector config as a secret.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client
USE CASES
01
Clearing the morning triage queue
List what is unassigned or overdue, set priorities, and route each one to an agent in the same pass.
02
Answering a customer who is waiting
Read the full thread first, then send the reply from the same place rather than retyping it in the helpdesk.
03
Handing a ticket to the right team
Reassign it and move it to the inbox that team watches.
04
Leaving context for whoever picks it up next
An internal note plus tags means the next agent starts from what you found, not from the customer's first message.
05
Raising a ticket from something that came up elsewhere
Create it with subject, requester and priority already set, so it lands triaged.
06
Reconstructing what happened on a disputed ticket
The activity history shows the order of replies, reassignments and state changes.
11 tools
Listed in project docs. Your client may show a different list.
get_ticketsget_ticketset_ticket_stateset_ticket_priorityset_ticket_tagsassign_ticketset_ticket_inboxget_ticket_activitiessend_replyadd_noteBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
Both documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
MCP Clients
Cursor, Other MCP clients
JSON
{
"mcpServers": {
"ticketdesk": {
"url": "https://api.ticketdesk.ai/mcp?apikey=<YOUR_APIKEY>"
}
}
}
