Trengo MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

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

Deletes · 9

Compare Registry entry

24 tools: 9 can delete or cancel things and 15 only read.

Scanned Oct 21, 2026

Deletes or cancels9Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads15Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

24 tools

Deletes or cancels 9Removes, cancels or revokes something.Claude Code: deny

trengo_assign_ticketAssign a ticket to a user or a team, with an optional assignment note.No findings
Why it is in this group
- The name "trengo_assign_ticket" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
Annotations the server declares
- title: Assign a ticket
- destructiveHint: true
trengo_close_ticketClose a ticket, optionally applying a ticket result (see trengo_list_ticket_results).No findings
Why it is in this group
- The name "trengo_close_ticket" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Close a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.
Annotations the server declares
- title: Close a ticket
- destructiveHint: true
trengo_create_board_cardCreate a card (e.g.No findings
Why it is in this group
- The name "trengo_create_board_card" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create a board card
- destructiveHint: true
trengo_create_contactCreate a contact on a channel.No findings
Why it is in this group
- The name "trengo_create_contact" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create a contact
- destructiveHint: true
trengo_create_ticketOpen a new ticket for an existing contact on a channel.No findings
Why it is in this group
- The name "trengo_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create a ticket
- destructiveHint: true
trengo_reopen_ticketReopen a closed ticket.No findings
Why it is in this group
- The name "trengo_reopen_ticket" says "reopen": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
Annotations the server declares
- title: Reopen a ticket
- destructiveHint: true
trengo_send_ticket_messagePost a message on a ticket.No findings
Why it is in this group
- The name "trengo_send_ticket_message" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Send a ticket message
- destructiveHint: true
trengo_update_board_cardPartially update a board card: rename it, move it to another stage, or set its users (owners) and contacts (leads).No findings
Why it is in this group
- The name "trengo_update_board_card" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Update a board card
- destructiveHint: true
trengo_update_contactRename a contact and/or set the contact groups it belongs to.No findings
Why it is in this group
- The name "trengo_update_contact" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.
Annotations the server declares
- title: Update a contact
- destructiveHint: true

Only reads 15Looks things up and changes nothing.Claude Code: allow

trengo_get_agent_performancePer-agent performance over a period: messages sent, notes, tickets assigned and closed, average first response and resolution times (with and without business hours).No findings
Why it is in this group
- The name "trengo_get_agent_performance" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Get agent performance
- readOnlyHint: true
trengo_get_contactFetch one contact with name, email, phone and custom field data, optionally with notes.No findings
Why it is in this group
- The name "trengo_get_contact" says "get": a word for reading.
Description, as the server wrote it
Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
Annotations the server declares
- title: Get a contact
- readOnlyHint: true
trengo_get_email_messageFetch the full email behind one message of a ticket: original HTML body, from, to, subject and Message-ID.No findings
Why it is in this group
- The name "trengo_get_email_message" says "get": a word for reading.
Description, as the server wrote it
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}.
Annotations the server declares
- title: Get an email message
- readOnlyHint: true
trengo_get_reporting_metricsAggregate support metrics over a period: new, created, assigned, closed and reopened tickets, average first response time and average total resolution time (seconds).No findings
Why it is in this group
- The name "trengo_get_reporting_metrics" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Get reporting metrics
- readOnlyHint: true
trengo_get_ticket_details_reportPer-ticket reporting rows: status, assignee, labels, first reply, first resolution and total resolution times (with and without business hours).No findings
Why it is in this group
- The name "trengo_get_ticket_details_report" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Get ticket details report
- readOnlyHint: true
trengo_list_contact_groupsList the contact groups in the account — use their ids with trengo_update_contact.No findings
Why it is in this group
- The name "trengo_list_contact_groups" says "list": a word for reading.
Description, as the server wrote it
List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
Annotations the server declares
- title: List contact groups
- readOnlyHint: true
trengo_list_contactsList contacts, or search them by name, email or phone number.No findings
Why it is in this group
- The name "trengo_list_contacts" says "list": a word for reading.
Description, as the server wrote it
List contacts, or search them by name, email or phone number. Trengo: GET /contacts.
Annotations the server declares
- title: List or search contacts
- readOnlyHint: true
trengo_list_custom_fieldsList the custom fields defined for tickets, contacts and profiles.No findings
Why it is in this group
- The name "trengo_list_custom_fields" says "list": a word for reading.
Description, as the server wrote it
List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
Annotations the server declares
- title: List custom fields
- readOnlyHint: true
trengo_list_labelsList the ticket labels (tags) in the account, for filtering tickets and reports.No findings
Why it is in this group
- The name "trengo_list_labels" says "list": a word for reading.
Description, as the server wrote it
List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
Annotations the server declares
- title: List labels
- readOnlyHint: true
trengo_list_quick_repliesList the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers.No findings
Why it is in this group
- The name "trengo_list_quick_replies" says "list": a word for reading.
Description, as the server wrote it
List the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.
Annotations the server declares
- title: List quick replies
- readOnlyHint: true
trengo_list_teamsList the teams in the account — use their ids to assign tickets to a team.No findings
Why it is in this group
- The name "trengo_list_teams" says "list": a word for reading.
Description, as the server wrote it
List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
Annotations the server declares
- title: List teams
- readOnlyHint: true
trengo_list_ticket_messagesList the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each.No findings
Why it is in this group
- The name "trengo_list_ticket_messages" says "list": a word for reading.
Description, as the server wrote it
List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.
Annotations the server declares
- title: List a ticket's messages
- readOnlyHint: true
trengo_list_ticket_resultsList the ticket results (closing outcomes, e.g.No findings
Why it is in this group
- The name "trengo_list_ticket_results" says "list": a word for reading.
Description, as the server wrote it
List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
Annotations the server declares
- title: List ticket results
- readOnlyHint: true
trengo_list_ticketsList tickets (conversations) visible to the token's user, newest activity first, with channel and latest message.No findings
Why it is in this group
- The name "trengo_list_tickets" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List tickets
- readOnlyHint: true
trengo_list_usersList the agents (users) in the Trengo account — use their ids to assign tickets or filter.No findings
Why it is in this group
- The name "trengo_list_users" says "list": a word for reading.
Description, as the server wrote it
List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
Annotations the server declares
- title: List users
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__trengo__trengo_list_tickets",
      "mcp__trengo__trengo_list_ticket_messages",
      "mcp__trengo__trengo_get_email_message",
      "mcp__trengo__trengo_list_contacts",
      "mcp__trengo__trengo_get_contact",
      "mcp__trengo__trengo_list_contact_groups",
      "mcp__trengo__trengo_list_users",
      "mcp__trengo__trengo_list_teams",
      "mcp__trengo__trengo_list_labels",
      "mcp__trengo__trengo_list_ticket_results",
      "mcp__trengo__trengo_list_custom_fields",
      "mcp__trengo__trengo_list_quick_replies",
      "mcp__trengo__trengo_get_reporting_metrics",
      "mcp__trengo__trengo_get_agent_performance",
      "mcp__trengo__trengo_get_ticket_details_report"
    ],
    "ask": [],
    "deny": [
      "mcp__trengo__trengo_create_ticket",
      "mcp__trengo__trengo_assign_ticket",
      "mcp__trengo__trengo_close_ticket",
      "mcp__trengo__trengo_reopen_ticket",
      "mcp__trengo__trengo_send_ticket_message",
      "mcp__trengo__trengo_create_contact",
      "mcp__trengo__trengo_update_contact",
      "mcp__trengo__trengo_create_board_card",
      "mcp__trengo__trengo_update_board_card"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as trengo. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/trengo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing