Trengo MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Trengo MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 24 tools. Last commit 10 Oct 2026.

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

Uptime history 13 days of history · worst day 99%

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

116 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

8 Oct a tool changed version

and 3 more, back to 8 October 2026

Trengo MCP by usefulapi missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 24

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trengo

trengo_assign_ticket

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

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

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

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

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

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

Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.

trengo_get_email_message

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

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

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_after_ticket_id instead of page. Trengo: GET /reporting/details/ticket.

trengo_list_contact_groups

List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.

trengo_list_contacts

List contacts, or search them by name, email or phone number. Trengo: GET /contacts.

trengo_list_custom_fields

List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.

trengo_list_labels

List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.

trengo_list_quick_replies

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

List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.

trengo_list_ticket_messages

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

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

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

List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.

trengo_reopen_ticket

Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.

trengo_send_ticket_message

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

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

Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://trengo.usefulapi.io/mcp	streamable-http	answering	149 ms	12 min ago

Alternatives to Trengo MCP by usefulapi

same job, measured the same way

HappyFox MCP by usefulapi

by usefulapi

Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.

23 tools answering

Benchmark Email MCP by usefulapi

by usefulapi

Manage Benchmark Email lists and contacts, and read campaign reports: opens, clicks, bounces.

25 tools answering

Textline MCP by usefulapi

by usefulapi

Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.

23 tools answering

EmailOctopus MCP by usefulapi

by usefulapi

Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.

13 tools answering

Sendlane MCP by usefulapi

by usefulapi

Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.

31 tools answering

Tito MCP by usefulapi

by usefulapi

Look up events, releases, tickets, registrations and discount codes, and edit tickets and codes.

20 tools answering

FreeAgent MCP by usefulapi

by usefulapi

Read FreeAgent contacts, invoices, bills, banking and reports; add contacts, draft invoices, time.

20 tools answering

Eventbrite MCP by usefulapi

by usefulapi

Manage Eventbrite events, ticket classes, venues and discounts; read attendees, orders and reports.

26 tools answering

Trengo MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Trengo MCP by usefulapi do?

It exposes 24 tools, read directly from the server on our last check. Among them: trengo_assign_ticket, trengo_close_ticket, trengo_create_board_card, trengo_create_contact, trengo_create_ticket, trengo_get_agent_performance and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trengo MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 116 ms. The bar chart above shows every period we have measured.

How do I connect Trengo MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trengo MCP by usefulapi need an API key?

No. Trengo MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trengo MCP by usefulapi?

It answers our handshake in 116 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Trengo MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.