Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Add to your MCP config, then reload & authorize:
{
"mcpServers": {
"trengo": {
"url": "https://trengo.usefulapi.io/mcp"
}
}
}| Tool | Type | What it does |
|---|---|---|
trengo_list_tickets | read | 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 | read | List 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. |
trengo_get_email_message | read | Get 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}. |
trengo_list_contacts | read | List or search contacts List contacts, or search them by name, email or phone number. Trengo: GET /contacts. |
trengo_get_contact | read | Get a contact Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}. |
trengo_list_contact_groups | read | List contact groups List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups. |
trengo_list_users | read | List users List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users. |
trengo_list_teams | read | List teams List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams. |
trengo_list_labels | read | List labels List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels. |
trengo_list_ticket_results | read | 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 | read | List custom fields List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields. |
trengo_list_quick_replies | read | 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_get_reporting_metrics | read | 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_agent_performance | read | 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 | read | 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_create_ticket | write | Create 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. |
trengo_assign_ticket | write | Assign 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. |
trengo_close_ticket | write | Close 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. |
trengo_reopen_ticket | write | Reopen a ticket Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen. |
trengo_send_ticket_message | write | Send 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. |
trengo_create_contact | write | Create 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. |
trengo_update_contact | write | Update 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}. |
trengo_create_board_card | write | Create 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. |
trengo_update_board_card | write | Update 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}. |
trengo_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
trengo_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Trengo tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Read-only; does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.