Is this an official Trengo MCP server?

No. It is Memtro's MCP server with Memtro's Trengo connector behind it: the connector reads Trengo through its API with the credentials you connect on Dashboard → Connections, and Trengo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Trengo?

Only when you ask, and only what it has been granted: add an internal note to a ticket (visible to agents only, never sent to the customer); reply to the customer on a ticket's channel (email, WhatsApp, chat); assign a ticket to an agent or a team; close a ticket, optionally with a ticket result; open a new ticket for a contact on a channel (sends nothing by itself); send an approved WhatsApp template to a phone number or a ticket's contact; create a contact on a channel; rename a contact or set its contact groups; delete a contact (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Support

Trengo MCP server

Trengo in any MCP client, through Memtro: Trengo does not publish this server. Memtro's Trengo connector reads Trengo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Trengo shared inbox: tickets by status, contact and date, a ticket's messages and internal notes, contacts by name or email, the agents and WhatsApp templates; can add an internal note, reply to the customer, assign, close or open a ticket, send a WhatsApp template, and create, rename or delete a contact.

Reads

trengo_ticketsTickets in the Trengo inbox, newest message first: status, subject, channel, contact id, assigned agent id, created, updated and closed times…
trengo_ticket_messagesA ticket's messages in order: inbound from the customer, outbound from an agent, or an internal NOTE, with the time…
trengo_contactsFind contacts by name, email or phone number: id, name and email (never the phone number).
trengo_usersThe agents (Trengo users): id, name and email.
trengo_whatsapp_templatesThe account's WhatsApp templates: id (the hsm_id trengo_send_whatsapp_template takes), title, status (only ACCEPTED can be sent), language, channel…

Acts, when you ask

These change something in Trengo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

trengo_add_internal_noteAdds an internal note to a Trengo ticket.
trengo_reply_to_ticketSends a reply to the customer on a Trengo ticket, on the ticket's own channel (an email, a WhatsApp message, a chat message…).
trengo_assign_ticketAssigns a Trengo ticket to an agent (user_id from trengo_users) or to a team (team_id, from Trengo's settings: the API has no team list).
trengo_close_ticketCloses a Trengo ticket, optionally recording a ticket result (its id from Trengo's settings).
trengo_create_ticketOpens a new Trengo ticket for a contact on a channel.
trengo_send_whatsapp_templateSends an approved WhatsApp template from Trengo, to a phone number or to the contact of an existing ticket.
trengo_create_contactCreates a Trengo contact on a channel, identified by an email address or a phone number as that channel uses.
trengo_update_contactRenames a Trengo contact or sets its contact groups (contact_group_ids replaces the groups it is in).
trengo_delete_contactPermanently deletes a Trengo contact.

Connect it

First connect Trengo on Dashboard → Connections, then add Memtro to your client once. The Trengo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Trengo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What's the latest on ticket 2501567?
› Which open tickets were updated since Monday?
› Show me every ticket from ada@acme.com.
› Add an internal note to ticket 2501567 saying the refund was approved.
› Reply to ticket 2501890 that the parcel left today.

Questions

Is this an official Trengo MCP server?: No. It is Memtro's MCP server with Memtro's Trengo connector behind it: the connector reads Trengo through its API with the credentials you connect on Dashboard → Connections, and Trengo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Trengo?: Only when you ask, and only what it has been granted: add an internal note to a ticket (visible to agents only, never sent to the customer); reply to the customer on a ticket's channel (email, WhatsApp, chat); assign a ticket to an agent or a team; close a ticket, optionally with a ticket result; open a new ticket for a contact on a channel (sends nothing by itself); send an approved WhatsApp template to a phone number or a ticket's contact; create a contact on a channel; rename a contact or set its contact groups; delete a contact (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.