MCP server

Trengo MCP by usefulapi

io.usefulapi/trengo

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.

Website Source

At a glance

Type

MCP server

Publisher

usefulapi.io (verified by the MCP Registry)

Status

Working at last check

Tools

24

Token cost

About 5,493 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http trengo https://trengo.usefulapi.io/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.trengo]
url = "https://trengo.usefulapi.io/mcp"

Gemini CLI

{"mcpServers":{"trengo":{"httpUrl":"https://trengo.usefulapi.io/mcp"}}}

Cursor

{"mcpServers":{"trengo":{"url":"https://trengo.usefulapi.io/mcp"}}}

VS Code

{"servers":{"trengo":{"type":"http","url":"https://trengo.usefulapi.io/mcp"}}}

Antigravity

agy mcp add trengo https://trengo.usefulapi.io/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"trengo","server_url":"https://trengo.usefulapi.io/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"trengo","server_url":"https://trengo.usefulapi.io/mcp"}

Tools

• trengo_assign_ticket ~248 tokens
  Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
• trengo_close_ticket ~168 tokens
  Close a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.
• trengo_create_board_card ~203 tokens
  Create a card (e.g. a deal or task) in a stage of a Trengo board. The board id is in the board's URL in Trengo. Trengo: POST /boards/{boardId}/cards.
• trengo_create_contact ~200 tokens
  Create a contact on a channel. The identifier is the contact's address on that channel: an email address for email channels, a phone number for WhatsApp/SMS/voice. Trengo: POST /channels/{channel_id}/contacts.
• trengo_create_ticket Sends messages · ~185 tokens
  Open a new ticket for an existing contact on a channel. Nothing is sent to the customer until you post a message with trengo_send_ticket_message. Trengo: POST /tickets.
• trengo_get_agent_performance ~382 tokens
  Per-agent performance over a period: messages sent, notes, tickets assigned and closed, average first response and resolution times (with and without business hours). Trengo: GET /reporting/agent_performance.
• trengo_get_contact ~140 tokens
  Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
• trengo_get_email_message ~180 tokens
  Fetch the full email behind one message of a ticket: original HTML body, from, to, subject and Message-ID. The message must be an email message. Trengo: GET /tickets/{ticket_id}/full_email_messages/{message_id}.
• trengo_get_reporting_metrics ~431 tokens
  Aggregate support metrics over a period: new, created, assigned, closed and reopened tickets, average first response time and average total resolution time (seconds). Filter by team, channel, label or direction. Trengo: GET /reporting/metrics.
• trengo_get_ticket_details_report ~796 tokens
  Per-ticket reporting rows: status, assignee, labels, first reply, first resolution and total resolution times (with and without business hours). Filter by team, channel, label, direction, status and created/closed/assigned date ranges; sort by a timing metric. For large accounts page with start_afte
• trengo_list_contact_groups ~114 tokens
  List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
• trengo_list_contacts ~163 tokens
  List contacts, or search them by name, email or phone number. Trengo: GET /contacts.
• trengo_list_custom_fields ~109 tokens
  List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
• trengo_list_labels ~109 tokens
  List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
• trengo_list_quick_replies ~121 tokens
  List the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.
• trengo_list_teams ~107 tokens
  List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
• trengo_list_ticket_messages ~166 tokens
  List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.
• trengo_list_ticket_results ~122 tokens
  List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
• trengo_list_tickets ~448 tokens
  List tickets (conversations) visible to the token's user, newest activity first, with channel and latest message. Filter by status, contact, assignee, channel, label, last message direction or update time. Trengo: GET /tickets.
• trengo_list_users ~146 tokens
  List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
• trengo_reopen_ticket ~101 tokens
  Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
• trengo_send_ticket_message Sends messages · ~322 tokens
  Post a message on a ticket. With internal_note=true it is an internal note visible only to agents. OTHERWISE IT IS DELIVERED TO THE CUSTOMER on the ticket's channel (email, WhatsApp, chat...) and cannot be recalled — confirm the text first. Trengo: POST /tickets/{ticket_id}/messages.
• trengo_update_board_card ~335 tokens
  Partially update a board card: rename it, move it to another stage, or set its users (owners) and contacts (leads). user_ids / contact_ids replace the current sets. Trengo: PUT /boards/{boardId}/cards/{cardId}.
• trengo_update_contact ~197 tokens
  Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.

Browse

• Email
• SMS and text messages
• WhatsApp

Related MCP servers

• eDesk MCP by usefulapi
  Work with eDesk support tickets, replies, internal notes, contacts and sales orders.
• Enchant MCP by usefulapi
  Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
• HappyFox MCP by usefulapi
  Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
• Teamleader Focus MCP by usefulapi
  Read Teamleader Focus contacts, companies, deals, invoices, projects; create deals, tasks.
• SupportBee MCP by usefulapi
  Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
• Re:amaze MCP by usefulapi
  Manage Re:amaze conversations, messages, contacts and help articles.
• Pobuca Connect MCP by usefulapi
  Read and update Pobuca Connect contacts and organizations; look up teams and custom fields.
• Simafri Suite
  Professional email, calendar, contacts and files on your own domain.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.usefulapi/trengo.svg)](https://aptlynx.net/servers/io.usefulapi/trengo)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents