io.usefulapi/trengo

up checked 2026-11-11T06:40:28.576Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Trengo MCP by usefulapi

Publisher-provided description

Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.

Summary by lookupd

Lets agents list, assign, reply to and close support tickets, manage contacts and boards, and pull support performance reports.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add trengo --url https://trengo.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (24 tools)

Publisher-provided 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,
• 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 /ti
• 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_replie
• 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 (sec
• 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 h
• 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,
• 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 /
• 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}/cl
• 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 cha
• 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/voi
• 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 s

Details

• Version: 1.37.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 425 ms
• First indexed: 2026-11-01T10:06:40.218Z
• Last seen in registry: 2026-11-11T00:17:36.204Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/trengo/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/trengo.svg)](https://lookupd.com/servers/io.usefulapi/trengo)

• 62092 servers
• Last crawl: 2026-11-11T17:17:22.074Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp