io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.1Updated Nov 14, 2026
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
The publisher's own server: Ably MCP by usefulapi
Hosted Trengo helpdesk connector: lets an assistant read tickets, contacts and reports, and reply, assign, close or reopen tickets.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Ftrengo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"trengo-by-usefulapi": {
"type": "http",
"url": "https://trengo.usefulapi.io/mcp"
}
}
}Use Trengo from Claude, Cursor, or any MCP client — read tickets and messages, look up contacts, users, teams and labels, pull support reports, and reply, assign, close or reopen tickets. Hosted, no local install: connect with your own Trengo credentials.
Live endpoint: https://trengo.usefulapi.io/mcp · Homepage: https://usefulapi.io/trengo
https://trengo.usefulapi.io/mcp.claude mcp add --transport http trengo https://trengo.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Trengo credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/trengo/
On first connect you'll provide your Trengo personal access token (Settings → Apps & integrations → Rest API). They're validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Each paid plan covers this server only. Ask your AI to run trengo_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with trengo_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with trengo_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Trengo.
Source: servers/trengo/README.md at commit f22f848
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.
pagesortuserslabelsstatuschannelscontact_idupdated_at_gtlast_message_typeList a ticket's 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.
pageticket_idrequiredGet an 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}.
ticket_idrequiredmessage_idrequiredList or search contacts
List contacts, or search them by name, email or phone number. Trengo: GET /contacts.
pageterminclude_last_interactionGet a contact
Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
contact_idrequiredinclude_notesList contact groups
List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
pageList users
List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
pagesortList teams
List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
pageList labels
List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
pageList ticket results
List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
pageList custom fields
List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
pageList 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.
typeGet 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.
metricsrequiredend_dateteam_idsdirectionlabel_idsstart_datechannel_idsGet 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.
pageend_dateteam_idsuser_idslabel_idsstart_datechannel_idsGet 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.
pagesort_bystatusesteam_idsdirectionlabel_idssort_orderchannel_idsclosed_end_datecreated_end_dateassigned_end_dateclosed_start_date+3 moreCreate a 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.
subjectchannel_idrequiredcontact_idrequiredAssign a ticket
Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
notetyperequiredteam_iduser_idticket_idrequiredClose a 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.
ticket_idrequiredticket_result_idReopen a ticket
Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
ticket_idrequiredSend a 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.
messagerequiredsubjectticket_idrequiredinternal_noteattachment_idsCreate a 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.
namechannel_idrequiredidentifierrequiredUpdate a 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}.
namecontact_idrequiredcontact_group_idsCreate a 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.
namerequiredboard_idrequiredstage_idrequireddescriptionUpdate a 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}.
namecard_idrequiredboard_idrequiredstage_iduser_idscontact_ids100% 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.
io.usefulapiOfficial publisher
Hosted MCP server for Ably that lets an assistant inspect realtime channels, presence and usage stats, publish messages, and review app configuration.
io.usefulapiOfficial publisher
Remote MCP server for Oyster that lets an assistant read team, time off, expense, contract and invoice data and approve or decline requests.
io.usefulapiOfficial publisher
Reads Avirato hotel PMS data — reservations, availability, rates, prices and meal plans — and records cash payments on bookings.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant list interview, participant and department metadata from a Willo account.
io.usefulapiOfficial publisher
Hosted MCP server that lets an assistant read Testlify hiring workspace details, assessments and assessment candidates.
{ "mcpServers": { "trengo": { "url": "https://trengo.usefulapi.io/mcp" } }}