Skip to content

SourcesClaude connector directoryAPI Tracker · publisher documentation

Read the Trengo setup guide →

Trengo logo

Trengo

Official

Connect Claude to Trengo, the customer engagement platform for email, WhatsApp, SMS, live chat, voice and social channels in one shared inbox. Claude works with the permissions of the signed-in Trengo user. It signs in over OAuth and calls the public Trengo API with that user's own token, so it sees and changes only what the user can. What you can do: - Tickets: find, read and summarise conversations, see what waits on your team, assign, label, close and reopen tickets, add internal notes and set reminders. - Messaging: send replies, WhatsApp templates and SMS, start new conversations, prepare email drafts for a person to send, and create WhatsApp templates for Meta review. - Contacts and profiles: search, create and update contacts, notes and contact groups. - AI agents: build and test Trengo AI agents, manage their knowledge and scenarios, and close knowledge gaps. - Journeys: design, check and publish automations. - Account setup: labels, teams, quick replies, custom fields, users and webhooks. - Reporting: ticket KPIs, time series, SLA details, agent performance and who is online. Safety by design: every tool that sends, deletes, merges or changes access is marked as destructive, so Claude asks you before it runs. The server refuses actions that Trengo or Meta would reject, such as free WhatsApp text outside the 24-hour window. The server stores no data and logs no message content.

87 tool names reported

Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.

Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established

  • account_overview
  • add_contact_note
  • add_internal_note
  • ai_agent_knowledge_gaps
  • ai_agent_report
  • assign_ticket
  • close_ticket
  • create_ai_agent
  • create_contact
  • create_journey
  • create_ticket
  • create_whatsapp_template
  • delete_ai_agent
  • delete_contact
  • delete_contact_note
  • delete_journey
  • delete_message
  • delete_ticket
  • deploy_ai_agent
  • favorite_ticket
  • get_agent_performance
  • get_ai_agent
  • get_boards
  • get_call
  • get_config
  • get_contact
  • get_inbox_counts
  • get_journey
  • get_journey_capabilities
  • get_message
  • get_profile
  • get_report_metrics
  • get_report_timeseries
  • get_ticket
  • get_ticket_link
  • get_ticket_messages
  • get_ticket_sla_details
  • label_ticket
  • list_ai_agent_knowledge
  • list_ai_agents
  • list_calls
  • list_deleted_tickets
  • list_journeys
  • list_tickets
  • list_whatsapp_templates
  • manage_ai_agent_knowledge_collections
  • manage_ai_agent_knowledge_sources
  • manage_ai_agent_scenarios
  • manage_ai_agent_snippets
  • manage_board_cards
  • manage_contact_groups
  • manage_custom_fields
  • manage_labels
  • manage_profile
  • manage_quick_replies
  • manage_teams
  • manage_ticket_results
  • manage_users
  • manage_webhooks
  • mark_mention_seen
  • mark_spam
  • mark_ticket_as_new
  • merge_tickets
  • move_ticket
  • prepare_email_draft
  • publish_journey
  • reopen_ticket
  • resolve_ai_agent_knowledge_gap
  • search_contacts
  • search_profiles
  • send_message
  • send_reply
  • send_sms
  • send_whatsapp_template
  • set_ticket_field
  • set_ticket_reminder
  • sms_overview
  • test_ai_agent
  • ticket_brief
  • unpublish_journey
  • update_ai_agent
  • update_contact
  • update_journey
  • waiting_on_us
  • watch_ticket
  • who_is_online
  • whoami

Choose a connection option

Remote endpointstreamable-http · OAuth 2.0
Official

Host setup required. Add https://mcp.trengo.com/mcp as a remote MCP server, choose OAuth and complete Trengo sign-in and consent. A Trengo account is required; no API key or pre-created administrator app is needed. The assistant registers when connecting. Review actions that send messages or change data. Account permissions and tool execution have not been runtime-tested by API Tracker.

https://mcp.trengo.com/mcpConfigure connection →
Connection source and version

Reported by Claude logoClaude connector directory

Remote endpointstreamable-http · OAuth 2.0
Official

Host setup required. Add https://mcp.trengo.com/mcp as a remote MCP server, choose OAuth and complete Trengo sign-in and consent. A Trengo account is required; no API key or pre-created administrator app is needed. The assistant registers when connecting. Review actions that send messages or change data. Account permissions and tool execution have not been runtime-tested by API Tracker.

https://mcp.trengo.com/mcpConfigure connection →
Connection source and version

Reported by API Tracker · publisher documentation

Sources and listing details

Source listings:

Grouping basis: reviewed. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.

Search API Tracker

Curated starting points