Back to Browse

Tickiti MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Connect AI assistants to the Tickiti helpdesk API: tickets, queries, reports and admin.

About

Connect AI assistants to the Tickiti helpdesk API: tickets, queries, reports and admin.

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-designed MCP server that acts as a thin, transparent shim over the Tickiti helpdesk API. The architecture properly delegates authentication and authorization to the upstream API via bearer tokens, with no credential mishandling or dangerous code patterns. Minor code quality observations (broad error handling, lack of input validation logging) are present but do not materially impact security. Permissions align appropriately with the server's purpose as a developer tool for API integration. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity).

3 files analyzed ยท 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-tickiti-tickiti-mcp": {
      "args": [
        "-y",
        "tickiti-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

tickiti-mcp

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 (/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: https://www.tickiti.com/docs/topic/mcp_server/

Tools

The ticket tools have full, validated inputs; the rest of the API is reachable through two general tools, so the whole surface is available without a separate tool per endpoint.

Tickets

ToolAbilityPurpose
create_tickettickets:writeOpen a ticket (subject+content, template, or intervention), with assignee, priority, status and participants; is_public is required
respond_to_tickettickets:writePost a response; change status, hold, assignee, priority, queue, subject, participants; send_full_email for the whole reply by email
close_tickettickets:writeClose, optionally with a final reply and a resolution
edit_responsetickets:writeChange a response in place (whole body, find/replace, visibility) with no notification โ€” or publish an internal note and notify
delete_responsetickets:writeSoft-delete a response
add_participants / remove_participantstickets:writeChange participants
delete_tickets / restore_tickettickets:writeDelete tickets (by number, or everything from one sender) and undo it
merge_ticketstickets:writeMerge two tickets (the older survives)
link_tickets / unlink_tickets / list_linked_ticketstickets:write / readThe Linked panel
move_responses / copy_responses / split_tickettickets:writeRepair a thread: move or copy responses, or split them off into a new linked ticket
change_originatortickets:writeChange who raised a ticket
delete_attachmenttickets:writeRemove one attachment (a malicious file, say), keeping a record of it
get_ticket / list_responsestickets:readA ticket's thread, participants and links; fields / max_body_chars keep long email threads small
get_responsetickets:readOne response by id
query_ticketstickets:readSearch tickets
query_responses / export_responsestickets:readResponses across tickets; counts and group-by tallies; NDJSON export to disk
get_attachment / download_attachmenttickets:readAttachment bytes (download streams any size to a file)
list_queues / list_teams / list_staff / list_resolutions / get_search_modestickets:readQueue names and settings, team keys, staff addresses, resolution categories, the search vocabulary

Settings, templates, mail, administration

ToolAbilityPurpose
list_perspectives / get_perspectivesettings:readSaved views, with conditions and sort orders
list_watchlistssettings:readWatchlists
list_stock_responses / get_stock_responsesettings:readStock responses (search, bodies)
create_stock_response / update_stock_response / delete_stock_responsesettings:writeEdit stock responses
get_template / search_templates / render_templatetemplates:readTemplates and FAQs; render one against data without sending
create_template / update_templatetemplates:writeEdit templates (updates change only the fields given)
upload_template_imagetemplates:write / settings:writeUpload an image for a template or stock response
send_email / search_sent_mailmail:write / mail:readSend mail; search what was sent
list_api_tokens / create_api_token / update_api_token / revoke_api_tokenadministration:*API keys (a token only grants abilities it holds)
list_workflowworkflow:readResolution categories, interventions, escalations
run_reportreports:readAnalytics reports
get_token_infoanyWhat this token can do: abilities, owner roles, plan
list_instancesโ€”The Tickiti instances configured (see below)
list_endpointsโ€”Every API endpoint, with abilities, path and body parameters
tickiti_callper endpointCall any /api/v1 endpoint by family and action

For anything beyond the named tools (mail, templates, workflow writes, administration, supervisor), the assistant uses list_endpoints to discover the action, then tickiti_call to run it โ€” covering all of the v1 API.

Requirements

  • Node.js 20 or newer
  • A Tickiti API token, minted from Administration โ†’ API keys, scoped to the abilities you want the assistant to have
  • An MCP-capable client โ€” e.g. Claude Code or the Claude desktop app

Install

git clone https://github.com/tickiti/tickiti-mcp.git
cd tickiti-mcp
npm install
npm run build

The built server is dist/server.js.

Configure

The server reads two environment variables (it fails fast on startup if either is missing):

VariablePurpose
TICKITI_API_BASEYour Tickiti install's public address, no trailing slash โ€” e.g. https://support.example.com. The server appends /api/v1/โ€ฆ.
TICKITI_API_TOKENThe bearer token. Its abilities determine what the assistant can do.

More than one instance

To reach several Tickiti installs from one server (production and staging, say), add TICKITI_INSTANCES: JSON, or the path of a JSON file, mapping a name to { "base", "token" }. The TICKITI_API_BASE / TICKITI_API_TOKEN pair stays the default instance, named by TICKITI_INSTANCE_NAME (default default).

TICKITI_INSTANCE_NAME=production
TICKITI_INSTANCES='{"staging": {"base": "https://staging.example.com", "token": "โ€ฆ"}}'

Every tool then takes an optional instance argument; list_instances shows the names.

Use with Claude Code

claude mcp add tickiti \
  --env TICKITI_API_BASE=https://support.example.com \
  --env TICKITI_API_TOKEN=YOUR_TICKITI_API_TOKEN \
  -- node /absolute/path/to/tickiti-mcp/dist/server.js

Confirm with claude mcp list (or /mcp in a session). Remove with claude mcp remove tickiti.

Other MCP clients configure servers in their own settings file, but the shape is the same: run node /absolute/path/to/tickiti-mcp/dist/server.js as a stdio server with TICKITI_API_BASE and TICKITI_API_TOKEN set in its environment.

Permissions & security

The server adds no permissions of its own. Every call runs as the staff user the token belongs to, gated by the token's abilities โ€” exactly as a direct API call would be. To limit what an assistant can do, mint a narrowly-scoped token:

  • A read-only token (e.g. tickets:read, reports:read) gives an assistant that can look but not change anything.
  • Grant write abilities only for the families the assistant needs to act on.
  • If a call is refused, the server reports the reason (missing ability, role or plan).

The ticket-writing tools send an idempotency key with every call, so a retried request never creates a duplicate ticket or response.

Long bodies can be given as content_path (a local file) instead of content, and files and images always go by path: the server reads them, so their bytes never pass through the model.

How it works

FileRole
src/client.tsRequest core: base URL, bearer auth, idempotency, error normalisation
src/result.tsMaps an API result into the MCP tool-result envelope
src/manifest.tsHelpers over the generated route manifest (lookup, path building)
src/generated/manifest.tsAuto-generated route table (do not edit)
src/tools/tickets.tsTicket writes โ€” verified input schemas
src/tools/ticket-reads.tsTicket, response and attachment reads
src/tools/ticket-operations.tsDelete, merge, link, move, originator, attachment delete, lookups
src/tools/settings-writes.tsStock responses and templates
src/tools/admin.tsMail, template rendering and images, perspectives, API keys, instances
src/tools/reads.tsNamed read tools (settings / workflow / reports)
src/tools/generic.tslist_endpoints + tickiti_call
src/param-hints.tsBody parameters list_endpoints shows for endpoints without a dedicated tool
src/server.tsEntry point: registers tools, connects the stdio transport
scripts/build-manifest.mjsRegenerates the manifest from the Tickiti route table

Maintainers

src/generated/manifest.ts is generated from Tickiti's own route table (php artisan route:list --json), so abilities, roles, plan gates and path params are never hand-maintained. Regenerate against a Tickiti checkout after the API changes:

TICKITI_DIR=/path/to/tickiti npm run manifest

There is an end-to-end sweep over every endpoint in tests/all-paths.mjs (npm run test:paths, needs a base URL and a full-ability token against a scratch instance), and an offline check of the tool registration in tests/smoke-tools.mjs (npm run build && node tests/smoke-tools.mjs).

Several tools call endpoints added to Tickiti in October 2026. Against an older install they return 404; list_endpoints describes the newest API.

License

MIT ยฉ Oxenic

Reviews

No reviews yet

Be the first to review this server!