Trengo MCP. Unify all customer conversations into one inbox.
Trengo MCP connects your customer service team to WhatsApp, email, chat, and social channels through one shared inbox. It lets your agent manage ticket lifecycles, check contact details, and send messages across every channel without switching apps.
Give Claude and any AI agent real-world access
You can list every open or closed ticket and create new ones with a single command.
Fetch the full message history for any specific ticket, including internal notes from your team.
Reply to customers or add private notes to a conversation thread across different channels.
List all available team members and check their current workload status.
Retrieve your entire customer database or verify that communication channels are set up correctly.
Ask an AI about this
Waiting for input…
What AI agents can do with Trengo MCP with 12 Tools
Use these tools to manage everything from listing all open support issues to sending direct messages and coordinating your entire team.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Trengo MCPCreate Ticket
Opens a brand new support ticket within Trengo.
Create Webhook
Sets up a new webhook to track specific conversation events in real time.
Get Account Profile
Retrieves information about the current user's profile within Trengo.
Get Ticket
Pulls up specific details for one existing support ticket.
List Channels
Lists all communication channels that are currently configured and active.
List Contacts
Retrieves a comprehensive list of all customers in your database.
List Messages
Shows the entire message history associated with a specific ticket.
List Tickets
Lists all current support tickets, allowing you to see which ones are open or closed.
List Team Members
Gets a list of all available team users and their current status.
List Webhooks
Lists the webhooks you have previously set up for event tracking.
Send Message
Sends a direct message to a customer via any connected channel.
Update Ticket
Changes the status of an existing ticket, like moving it from OPEN to CLOSED.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Trengo, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Trengo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of juggling multiple support channels
Right now, when an issue comes in through WhatsApp, your team has to switch apps. Then they go to the email client to see if the customer replied there too. They might open a dedicated chat widget just for live issues. This constant app jumping means lost context, slow response times, and manual data entry across five different tabs.
With this MCP, all those channels feed into one unified view. Your AI agent sees everything—WhatsApp messages, emails, chats—as one continuous conversation thread. The result is that your team stops chasing down threads and starts solving problems.
Manage conversations with the Trengo MCP
The tedious steps of checking contacts in a separate tab, manually logging into another service just to check status, or having to copy 50 lines of chat history are gone. Your agent handles that background coordination.
You simply tell your AI client what needs doing—'Close this ticket and notify the team lead.' It executes all the required steps automatically using update_ticket, list_team_members, and sending messages in a single flow.
What Trengo MCP does for your AI
Managing customer conversations used to mean logging into five different dashboards just to see a single issue's full history. This MCP changes that by giving you a unified view of all incoming communication—whether it arrived via email, WhatsApp, or live chat. You can use your agent to quickly list every ticket and pull up the entire message history for any contact in one place.
Need to update something? Your agent handles status changes and internal notes automatically. It even lets you query team member lists so you know who's available right now. By connecting this MCP through Vinkius, you get a single point of control over your whole support operation, letting your AI client handle the heavy lifting for coordination, ticketing, and messaging.
019dd179-8267-737c-a3d0-c2a4052b6672 How to set up Trengo MCP
The bottom line is that you talk to your AI client how you normally talk to a coworker; it does the rest of the work in Trengo.
Subscribe to this MCP and provide the Trengo API Token, which you find in your account settings.
Connect your preferred AI client (like Cursor or Claude) to Vinkius. Your agent now has access to all the communication tools.
Ask your agent a natural language question, like 'List all open billing tickets' or 'Send a follow-up message to John Doe'.
Who uses Trengo MCP
Support Managers and Operations Leads who are tired of context switching between email, chat apps, and ticketing systems. This MCP is for people whose job depends on having a complete, real-time view of customer interactions across every possible channel.
Responding to inquiries by pulling up ticket history from WhatsApp or email and updating the status as 'RESOLVED' without leaving the chat window.
Coordinating communication channels, running reports on team availability using list_team_members, and setting up webhook events to track system activity.
Quickly reviewing ticket histories across all platforms to monitor overall team performance and identify bottlenecks in the support process.
Benefits of connecting Trengo MCP
Stop context switching. Instead of jumping between email, WhatsApp web, and your ticketing system, you use a single chat interface to manage everything.
Instantly access full history using list_messages. When an agent takes over a ticket, they don't waste time searching; the entire conversation is immediately available.
Maintain accuracy when closing tickets. Use update_ticket to change statuses and add internal notes, ensuring compliance and a clear audit trail for every interaction.
Coordinate faster with your team. list_team_members lets you check who is available or who owns a specific account before assigning the ticket.
Never miss a communication event. The webhook tools allow you to monitor conversations in real-time, letting your agent trigger actions as soon as something happens.
Trengo MCP use cases
Needing full context for an escalated issue
A customer reports a major outage via social media. Instead of manually searching three different systems, the agent asks their AI client to list_contacts and then use list_messages on that contact ID. The AI pulls up the last 5 messages from email, chat, and WhatsApp instantly, giving the team lead all the context needed for an accurate response.
Handling a backlog of old tickets
The Ops Lead needs to clean up old support requests. They ask their agent to list_tickets, filter by 'OPEN', and then use update_ticket on the results, setting them all to 'PENDING' status with a note explaining the follow-up required.
Sending a proactive follow-up
A ticket was resolved last week but nothing happened. The agent asks their AI client to send_message to that customer ID, reminding them of the resolution and asking if they need anything else. This is all done without needing the customer's direct email address.
Onboarding a new team member
A new support rep needs to know who is available right now. They ask their agent to list_team_members, and the AI client provides an immediate status report showing who is online and how many tickets they currently own.
Trengo MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Copy/pasting history manually
A user sees a conversation in email, copies the text, switches to chat, pastes it, then opens the ticketing system and pastes it there too. The result is lost context and wasted time.
Use your agent to list_messages on the ticket ID. This pulls all history—email, chat, social—into one view automatically. Then use send_message to reply directly from that single pane of glass.
Forgetting the status update
A conversation is resolved, but the user forgets to manually change the ticket status in the system, leaving it stuck as 'OPEN' and blocking reporting.
After resolving the issue, tell your agent to execute update_ticket. This automatically changes the status (e.g., to CLOSED) and ensures proper record-keeping.
Using multiple tokens/API keys
Trying to connect Trengo via one client for chat data, and then connecting a separate service just for email data.
Connect this MCP through Vinkius. It centralizes all your communication tools under one roof, letting your agent talk to every channel simultaneously.
When to use Trengo MCP
Use this MCP if the core problem is fragmented customer data. If you handle support across WhatsApp, email, and chat, but your current process requires switching between different dashboards or copying/pasting conversations, this is for you. You need a single source of truth. Don't use this if your only goal is pure internal knowledge management; in that case, an internal documentation tool might be better. Also, don't rely on it to write the responses—it manages the data and status updates. For drafting perfect copy, you still need a dedicated writing assistant, but for coordinating the message delivery itself, this MCP is essential.
Frequently asked questions about Trengo MCP
How does Trengo MCP handle conversations? +
It gives you one unified inbox to view all incoming communications from WhatsApp, email, chat, and social media. This means your agent sees every message in the same place, regardless of where it originated.
Can I use Trengo MCP to update ticket statuses? +
Yes, you can use the update_ticket tool. Your agent changes the status (e.g., OPEN to CLOSED) and adds internal notes, keeping your records clean and accurate.
What if I need to check who on my team is available? +
You can use list_team_members. Your agent queries this tool to give you a real-time report on which users are online or currently handling tickets, speeding up assignment.
Does Trengo MCP let me send messages outside of a ticket? +
Absolutely. The send_message tool lets your agent communicate with customers directly across various configured channels, even if there isn't an active support ticket running.
How do I get the full history for a complex issue using Trengo MCP? +
Use list_messages. This tool pulls the entire conversation transcript—including customer queries and internal team notes—for one specific ticket, giving you total context immediately.