Trengo MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://trengo.usefulapi.io/mcp

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

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

{
  "servers": {
    "trengo": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}

https://trengo.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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.

• 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_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; sort by a timing metric. For large accounts

• 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_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: POST /tickets/{ticket_id}/messa

• 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}.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 14 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 24 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32461 servers in this category
• Published to the registry more recently than 96% of the other 32461 servers in this category
• Basic checks equal to or better than 100% of the other 32461 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{