Sinch Engage / MessageMedia MCP server

Sinch Engage / MessageMedia MCP server is an MCP server that exposes Sinch Engage and Sinch MessageMedia messaging and reporting APIs to LLM clients. Designed for developers, marketing teams, and support agents using AI assistants, it enables direct control over enterprise communication workflows from chat interfaces. The server provides tools to send outbound SMS messages to mobile numbers formatted in E.164 notation. Users can query real-time analytics, fetching both detailed and summary reports for sent and received messages across specified date ranges, or trigger asynchronous report exports for large data volumes. Additionally, the server connects to Sinch Engage contact management endpoints, enabling models to look up recipients by name or phone number, create and update contacts, and organize contacts into lists and groups. Operators can limit which capabilities are exposed by setting category and operational permission filters in their client configuration.

Category: Communication & Messaging

Tags: messagemedia, messaging, notifications, sinch, sms

Visit Sinch Engage / MessageMedia MCP server

How to install and configure Sinch Engage / MessageMedia MCP server

1. Ensure Node.js 16.0 or higher is installed and you have an active Sinch Engage account. 2. Obtain your API key and secret from your Sinch Engage API settings. 3. Open your Claude Desktop configuration file (claude_desktop_config.json). 4. Add the server under the mcpServers object using npx: json { "mcpServers": { "Sinch Engage": { "command": "npx", "args": ["-y", "@sinch-engage/mcp-server"], "env": { "SINCH_ENGAGE_API_KEY": "<your-key>", "SINCH_ENGAGE_API_SECRET": "<your-secret>", "SINCH_ENGAGE_REGION": "<region>", "MCP_TOOL_CATEGORIES": "reporting, contacts, messaging", "MCP_TOOL_MODES": "read, write, delete" } } } } 5. Replace <your-key>, <your-secret>, and <region> (such as EU or AU) with your credentials, then restart Claude Desktop.

What you can do with Sinch Engage / MessageMedia MCP server

• Send transactional SMS alerts or one-time passcodes directly to mobile phone numbers formatted in standard E.164 notation. - Generate detailed or summary message delivery reports across custom date ranges to analyze outbound campaign performance. - Request and track asynchronous large-scale message report exports, checking status and fields before downloading complete logs. - Search contact directories by name, phone number, or group to quickly verify customer profiles within AI workflows. - Create and manage contact groups to organize distribution lists for marketing communications and notifications.

Key facts

• https://github.com/messagemedia/sinch-engage-mcp-server
• Communication & Messaging, CRM, ERP & E-commerce
• messagemedia, messaging, notifications, sinch, sms

Part of MCP Servers

How do I install the Sinch Engage / MessageMedia MCP server?

You can install and run the server using npx by referencing the @sinch-engage/mcp-server package in your client configuration. Alternatively, you can clone the repository from GitHub, run npm install, and execute the local index.js script directly with Node.js.

What can the Sinch Engage / MessageMedia MCP server do?

The server enables LLM agents to send SMS messages, retrieve detailed and summary message logs, request async export reports, and manage contacts and contact groups via standard Sinch Engage APIs.

Which MCP clients work with Sinch Engage / MessageMedia MCP server?

The server is built on the Model Context Protocol standard and works with Claude Desktop as well as any other MCP-compliant host application that supports standard input/output server connections.

Which regions are supported by the Sinch Engage MCP server?

The server currently supports EU and AU regions. You must set the SINCH_ENGAGE_REGION environment variable to either EU or AU depending on where your Sinch Engage or MessageMedia account is provisioned.

Can I limit which tools the MCP server exposes?

Yes. You can control exposed tools by configuring the MCP_TOOL_CATEGORIES variable with values like reporting, contacts, or messaging, and the MCP_TOOL_MODES variable with read, write, or delete permissions.