Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"trengo": {
"url": "https://trengo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"trengo": {
"type": "http",
"url": "https://trengo.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Trengo personal access token.
Create one in Trengo → Settings → Apps & integrations → Rest API → new personal access token. It acts with your own Trengo permissions, channels and teams. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
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: the login page asks for your Trengo personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Trengo connector, then ask in plain words. The AI picks the tools.
| 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 usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
trengo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Trengo tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
trengo_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Trengo (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
trengo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Trengo Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run trengo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Trengo server only. Subscribe with trengo_upgrade (it returns a Stripe Checkout link). Cancel any time with trengo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running trengo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Trengo. The server calls the Trengo API with your own Trengo access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Trengo personal access token. See Before you connect for where to find it.
No. 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: the login page asks for your Trengo personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Trengo API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Trengo.
Yes, if you approve it. 9 of the 24 Trengo tools can create or change data. The other 15 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Trengo server only. Cancel any time: Pro then runs to the end of the paid period. Run trengo_usage_status to see how many calls you used.
Ask the AI to run trengo_upgrade: it returns a Stripe Checkout link. To cancel, run trengo_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with trengo_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
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.