# Trengo MCP > 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. ## Overview - **Category:** communication-messaging - **Price:** Free - **Tags:** omnichannel-inbox, helpdesk-ticketing, shared-inbox, customer-service, live-chat, whatsapp-integration ## Description 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. ## Tools ### create_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. ## Prompt Examples **Prompt:** ``` List all currently open support tickets. ``` **Response:** ``` I've retrieved your open tickets. You have 4 active conversations including 'Billing issue' from John Doe, 'Login error' from Smith, and 2 others. Which one would you like to see the messages for? ``` **Prompt:** ``` Show me the last 3 messages for ticket #88231. ``` **Response:** ``` I've fetched the history. The last 3 messages include: a customer query about shipping, your team's response, and an internal note regarding the tracking number. Shall I reply to the customer? ``` **Prompt:** ``` Close ticket #10293 as 'CLOSED' and add a note 'Resolved via AI'. ``` **Response:** ``` Ticket updated! I've set the status of ticket 10293 to 'CLOSED' and added your internal note. The conversation has been archived successfully. ``` ## Capabilities ### Manage all tickets You can list every open or closed ticket and create new ones with a single command. ### Handle conversations Fetch the full message history for any specific ticket, including internal notes from your team. ### Send messages Reply to customers or add private notes to a conversation thread across different channels. ### Coordinate the team List all available team members and check their current workload status. ### Manage contacts Retrieve your entire customer database or verify that communication channels are set up correctly. ## 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. ## Benefits - 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. ## How It Works 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. 1. Subscribe to this MCP and provide the Trengo API Token, which you find in your account settings. 2. Connect your preferred AI client (like Cursor or Claude) to Vinkius. Your agent now has access to all the communication tools. 3. Ask your agent a natural language question, like 'List all open billing tickets' or 'Send a follow-up message to John Doe'. ## Frequently Asked Questions **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.