Trengo MCP by usefulapi
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close
Reviews
No review yet. Used Trengo MCP by usefulapi? Be the first to help others choose.What it does
Trengo MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://trengo.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http trengo https://trengo.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"trengo": {
"url": "https://trengo.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE Trengo MCP by usefulapi answered an MCP connection on 13 Nov 2026 and introduced itself as trengo-mcp 1.39.1 (MCP protocol 2025-06-18).
24 tools offered to AI assistants
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_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_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_list_contacts· List contacts, or search them by name, email or phone number. Trengo: GET /contacts.trengo_get_contact· Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.trengo_list_contact_groups· List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.trengo_list_users· List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.trengo_list_teams· List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.trengo_list_labels· List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.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_custom_fields· List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.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.
Show 12 more
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/metritrengo_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_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; sorttrengo_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_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_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_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_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}.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_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}.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.39.2 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://trengo.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://usefulapi.io/trengo/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.1 → 1.39.0
- VERSION11 Nov 20261.38.0 → 1.38.1
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
- VERSION28 Oct 20261.26.0 → 1.27.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Trengo MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Trengo MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Trengo MCP by usefulapi
How do I connect Trengo MCP by usefulapi?
Use the hosted endpoint https://trengo.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Trengo MCP by usefulapi offer?
When Electra Index connected on 13 Nov 2026, it listed 24 tools: trengo_list_tickets, trengo_list_ticket_messages, trengo_get_email_message, trengo_list_contacts, trengo_get_contact, trengo_list_contact_groups, trengo_list_users, trengo_list_teams and more. The full list is in "Live check" above.
Is Trengo MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.