[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Trengo MCP tools

> The Trengo MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/trengo

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Trengo has 13 operations on the Cotlet MCP server, in trengo_read and trengo_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `trengo_read`, `trengo_write`
- Connects with: Your own Trengo login at app.trengo.com. What your agent can do follows your user's permissions. You enter your 2-step verification yourself, in your own Cloud Browser.
- Integration page: https://cotlet.dev/integrations/trengo-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_conversations`](https://cotlet.dev/docs/mcp/trengo/list_conversations.md) | Conversations in an inbox folder, with channel, labels, assignee and the last message. |
| [`search_conversations`](https://cotlet.dev/docs/mcp/trengo/search_conversations.md) | Conversations that match a ticket number, name, phone number, email address or keywords. |
| [`get_conversation`](https://cotlet.dev/docs/mcp/trengo/get_conversation.md) | One conversation with its contact, labels, assignee and every message, internal notes included. |
| [`list_labels`](https://cotlet.dev/docs/mcp/trengo/list_labels.md) | The labels set up in your Trengo, with colour, channels and whether they are archived. |
| [`list_assignees`](https://cotlet.dev/docs/mcp/trengo/list_assignees.md) | The users and teams a conversation can be assigned to. |
| [`list_quick_replies`](https://cotlet.dev/docs/mcp/trengo/list_quick_replies.md) | The quick replies of your Trengo with their type and text. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`add_label`](https://cotlet.dev/docs/mcp/trengo/add_label.md) | Adds a label to a conversation. |
| [`remove_label`](https://cotlet.dev/docs/mcp/trengo/remove_label.md) | Removes a label from a conversation. |
| [`set_reminder`](https://cotlet.dev/docs/mcp/trengo/set_reminder.md) | Sets or clears the reminder that reopens a conversation in your inbox. |
| [`add_internal_note`](https://cotlet.dev/docs/mcp/trengo/add_internal_note.md) (Confirm) | Writes an internal note on a conversation, visible to your team and not to the customer. |
| [`assign_conversation`](https://cotlet.dev/docs/mcp/trengo/assign_conversation.md) (Confirm) | Assigns a conversation to a user or to a team. |
| [`reply_to_conversation`](https://cotlet.dev/docs/mcp/trengo/reply_to_conversation.md) (Confirm) | Sends a reply to the customer in the conversation's own channel. |
| [`close_conversation`](https://cotlet.dev/docs/mcp/trengo/close_conversation.md) (Confirm) | Closes a conversation without sending a message. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.