Mcp Tomticket

io.github.gliraPublished by GitHub account glirav1.0.0Updated Oct 25, 2026

TomTicket helpdesk MCP: tickets, replies, time, customers, chats, and KB

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Local MCP server for the TomTicket helpdesk API, letting an assistant list, reply to, time and finish tickets and browse customers, chats and the knowledge base

What you can do
List open or filtered tickets and read a ticket's details, replies and logged time entries. Reply to tickets, add internal comments, start and close status timers, and finish tickets with time worked. Create, transfer and assign tickets to operators. Browse customers, organizations, departments, chats, knowledge base and custom fields.
When to use it
Useful when a support team works in TomTicket and wants an assistant to triage the queue, draft or post replies, log hours and close tickets without switching to the web panel.
Requirements
Runs locally via npx with Node.js 18 or newer. Needs a TomTicket API Bearer Token in TOMTICKET_TOKEN, created in the account panel, and a Premium or Enterprise account. TOMTICKET_BASE_URL is optional and defaults to the public API endpoint. Network access to the TomTicket API is required.
Before you install
The token must be granted create-and-modify permission for replies, time logging and finishing, so the assistant can change production helpdesk data. Write operations warn that they affect production. Finishing a ticket requires an assigned operator. Keep the token in the environment variable only and never commit it. The API allows 3 requests per second.

Installation

In SourceWeft

  1. Open Mcp Tomticket in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-tomticket

[npm] [MCP Registry] [Glama]

Servidor MCP para a API TomTicket v2. Lista, responde, lança horário e finaliza chamados e também cobre clientes, organizações, chats, departamentos e base de conhecimento.

Não existe endpoint de login. O Bearer Token é criado no painel: Administração → Configurações da Conta → API → Novo Token. Marque Pode criar e modificar dados para respostas, horário e finalização.

O token vai só em variável de ambiente. Nunca o commite.

Requisitos

  • Node.js >= 18
  • Token de API do TomTicket (conta Premium/Enterprise)

Instalação

Via npm (recomendado):

bash
npx mcp-tomticket

No Cursor (~/.cursor/mcp.json):

json
{  "mcpServers": {    "tomticket": {      "command": "npx",      "args": ["-y", "mcp-tomticket"],      "env": {        "TOMTICKET_TOKEN": "cole-o-token-aqui"      }    }  }}

Clone local:

bash
git clone https://github.com/glira/mcp-tomticket.gitcd mcp-tomticketnpm installcp .env.example .env# edite .env e cole o TOMTICKET_TOKENnpm run build

Validação rápida (somente leitura):

bash
npm run smoke

Opcional — cria, comenta, responde e finaliza um chamado de teste com assunto [MCP TESTE]:

bash
npx tsx scripts/smoke.ts --write

Recarregue os MCPs em Settings → MCP. Exemplo local em .cursor/mcp.json.example.

Tools principais

ToolAção
tomticket_list_open_ticketsChamados abertos
tomticket_list_ticketsTodos, com filtros
tomticket_get_ticketDetalhe + respostas + horários
tomticket_reply_ticketResposta do atendente (start_date/end_date lançam horário)
tomticket_comment_ticketComentário interno
tomticket_finish_ticketFinaliza (time_work em minutos)
tomticket_start_status / tomticket_close_statusCronômetro de status
tomticket_create_ticketAbre chamado
tomticket_transfer_ticket / tomticket_assign_operatorTransferir / vincular atendente

Há também tools de clientes, organizações, chats, departamentos, KB e campos personalizados. Operações de escrita avisam que alteram produção. Finalizar um chamado exige atendente vinculado (tomticket_assign_operator).

Rate limit

A API aceita 3 requisições por segundo. O client aplica intervalo mínimo de 350 ms.

Variáveis

VariávelObrigatóriaDescrição
TOMTICKET_TOKENsimBearer Token do painel
TOMTICKET_BASE_URLnãoPadrão https://api.tomticket.com/v2.0

Licença

MIT

Source: README.md at commit 4602c77

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts