Connect AI assistants to the Tickiti helpdesk API: tickets, queries, reports and admin.
An MCP (Model Context Protocol) server that exposes the Tickiti helpdesk API to AI assistants such as Claude. It is a thin shim over the Tickiti Public API v1 (): each MCP tool forwards to a v1 endpoint, adding your bearer token and — for writes — an idempotency key. The token's abilities are the security boundary: the server only relays calls, it never widens them, so a read-only token gives a…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
list_endpointsNo description publishedThis tool published no description. Forge does not invent one.
tickiti_callNo description publishedThis tool published no description. Forge does not invent one.
list_workflowNo description publishedThis tool published no description. Forge does not invent one.
run_reportNo description publishedThis tool published no description. Forge does not invent one.
get_ticketNo description publishedThis tool published no description. Forge does not invent one.
list_responsesNo description publishedThis tool published no description. Forge does not invent one.
get_attachmentNo description publishedThis tool published no description. Forge does not invent one.
query_responsesNo description publishedThis tool published no description. Forge does not invent one.
export_responsesNo description publishedThis tool published no description. Forge does not invent one.
create_ticketNo description publishedThis tool published no description. Forge does not invent one.
respond_to_ticketNo description publishedThis tool published no description. Forge does not invent one.
query_ticketsNo description publishedThis tool published no description. Forge does not invent one.
mcp_interventionNo description publishedThis tool published no description. Forge does not invent one.
0 of 13 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
An MCP (Model Context Protocol) server that exposes the Tickiti helpdesk API to AI assistants such as Claude. It is a thin shim over the Tickiti Public API v1 (): each MCP tool forwards to a v1 endpoint, adding your bearer token and — for writes — an idempotency key. The token's abilities are the security boundary: the server only relays calls, it never widens them, so a read-only token gives a read-only assistant. 📖 Full documentation: The ticket tools have full, validated inputs; the rest of…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.