Trengo MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 5 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 24 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 18600 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 18600 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 18600 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{