Index / MCP servers / Trengo MCP by usefulapi

Trengo MCP by usefulapi MCP server

Trengo MCP by usefulapi is a remote MCP server that gives an AI agent 24 tools, among them trengo_assign_ticket, trengo_close_ticket, trengo_create_board_card. It answers at https://trengo.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.

Status
Answering
Tools
24
Official
yes, served from usefulapi.io
Reliability
4 of 4 checks
Response time
104 ms
Transport
streamable HTTP
Last checked
15 November 2026

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

Description as the publisher wrote it.

The 24 tools Trengo MCP by usefulapi offers

ToolWhat it does
trengo_assign_ticketAssign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
Inputs: ticket_id, type, user_id, team_id, note
trengo_close_ticketClose a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.
Inputs: ticket_id, ticket_result_id
trengo_create_board_cardCreate 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.
Inputs: board_id, stage_id, name, description
trengo_create_contactCreate 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.
Inputs: channel_id, identifier, name
trengo_create_ticketOpen 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.
Inputs: channel_id, contact_id, subject
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). Trengo: GET /reporting/agent_performance.
Inputs: start_date, end_date, team_ids, channel_ids, label_ids, user_ids
trengo_get_contactFetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
Inputs: contact_id, include_notes
trengo_get_email_messageFetch 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}.
Inputs: ticket_id, message_id
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). Filter by team, channel, label or direction. Trengo: GET /reporting/metri
Inputs: metrics, start_date, end_date, team_ids, channel_ids, label_ids
trengo_get_ticket_details_reportPer-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
Inputs: statuses, team_ids, channel_ids, label_ids, direction, created_start_date
trengo_list_contact_groupsList the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
Inputs: page
trengo_list_contactsList contacts, or search them by name, email or phone number. Trengo: GET /contacts.
Inputs: term, include_last_interaction, page
trengo_list_custom_fieldsList the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
Inputs: page
trengo_list_labelsList the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
Inputs: page
trengo_list_quick_repliesList the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.
Inputs: type
trengo_list_teamsList the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
Inputs: page
trengo_list_ticket_messagesList the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.
Inputs: ticket_id, page
trengo_list_ticket_resultsList the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
Inputs: page
trengo_list_ticketsList 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.
Inputs: status, contact_id, users, channels, labels, last_message_type
trengo_list_usersList the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
Inputs: sort, page
trengo_reopen_ticketReopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
Inputs: ticket_id
trengo_send_ticket_messagePost 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.
Inputs: ticket_id, message, internal_note, subject, attachment_ids
trengo_update_board_cardPartially 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}.
Inputs: board_id, card_id, name, stage_id, user_ids, contact_ids
trengo_update_contactRename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.
Inputs: contact_id, name, contact_group_ids

Add Trengo MCP by usefulapi to your AI client

Every block below points at https://trengo.usefulapi.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http trengo-mcp-by-usefulapi https://trengo.usefulapi.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://trengo.usefulapi.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "trengo-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "trengo-mcp-by-usefulapi": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "serverUrl": "https://trengo.usefulapi.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Trengo MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
  - name: Trengo MCP by usefulapi
    type: streamable-http
    url: https://trengo.usefulapi.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "httpUrl": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "trengo-mcp-by-usefulapi": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Ftrengo.usefulapi.io%2Fmcp&type=streamable_http&id=trengo-mcp-by-usefulapi&name=Trengo%20MCP%20by%20usefulapi

Is Trengo MCP by usefulapi up right now?

It answered our last check on 15 November 2026 in 104 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Trengo MCP by usefulapi

Questions about Trengo MCP by usefulapi

Is there an official Trengo MCP by usefulapi MCP server?

Yes. It is published by usefulapi.io and served from trengo.usefulapi.io, the vendor's own domain: https://trengo.usefulapi.io/mcp.

How many tools does Trengo MCP by usefulapi have?

24, as returned by the server's own tools/list on 18 November 2026: trengo_assign_ticket, trengo_close_ticket, trengo_create_board_card, trengo_create_contact, trengo_create_ticket, trengo_get_agent_performance, trengo_get_contact, trengo_get_email_message, and 16 more.

Is Trengo MCP by usefulapi down?

It answered our last check on 15 November 2026 in 104 ms. Over 4 checks since 29 September 2026 it answered 4.

How do I add Trengo MCP by usefulapi to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://trengo.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Trengo MCP by usefulapi need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.usefulapi. Endpoint host: trengo.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:trengo. First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.