Bring Omnichannel Inbox
to Claude Code
Learn how to connect Trengo to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Trengo MCP Server?
Connect your Trengo omnichannel inbox to any AI agent and simplify how you manage customer conversations, team collaboration, and support tickets through natural conversation.
What you can do
- Unified Inbox Management — List all tickets and conversations across WhatsApp, Email, and Chat in one place.
- Ticket Control — Create new support tickets, update statuses (OPEN, CLOSED, ASSIGNED), and manage assignments via AI.
- Omichannel Messaging — Send messages to customers or add internal team notes to any conversation.
- Contact & Channel Directory — List your customer database and verify all configured communication channels.
- Team Coordination — Query team member lists to understand availability and workload.
- Event Monitoring — List and create webhooks to track conversation events in real-time.
How it works
1. Subscribe to this server
2. Enter your Trengo API Token (found in your account profile or settings)
3. Start managing your unified inbox from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Support Managers — quickly retrieve ticket histories and monitor team activity via simple AI commands.
- Customer Success Teams — respond to inquiries and update ticket statuses directly from the workspace.
- Operations Leads — coordinate communication channels and monitor webhook events via the AI assistant.
Built-in capabilities (12)
Create a new ticket
Create a new webhook
Get current user profile
Get ticket details
). List communication channels
List all contacts
List ticket messages
List team users
List all support tickets
List configured webhooks
Send a message
Update ticket status
Why Claude Code?
Claude Code registers Trengo as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Trengo data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Trengo tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Trengo in Claude Code
Trengo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Trengo to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Trengo in Claude Code
The Trengo MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Trengo for Claude Code
Every tool call from Claude Code to the Trengo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the messages in a specific ticket via AI?
Yes! Use the list_messages tool and provide the Ticket ID. Your agent will retrieve the full conversation history, including both customer messages and internal notes.
How do I add an internal note to a ticket that the customer won't see?
Use the send_message action. Provide the Ticket ID and your text, and set the internal parameter to 'true'. This will log the message as a private note for your team.
Is it possible to list all communication channels like WhatsApp and Email?
Absolutely. Use the list_channels query. The agent will retrieve all your active integrations, helping you identify which Channel ID to use when creating new tickets.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
