Sinch Engage (Sinch MessageMedia in AU) MCP server, which provides Sinch Engage APIs as MCP tools.
Sinch Engage / MessageMedia MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Sinch Engage (Sinch MessageMedia in AU) MCP server, which provides Sinch Engage APIs as MCP tools.
Once Sinch Engage / MessageMedia is connected, these are the calls the assistant has available:
Messaging — The Messaging tool exposed by this serverReporting — The Reporting tool exposed by this serverContacts — The Contacts tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverYou will need 5 environment variables: SINCH_ENGAGE_API_KEY, SINCH_ENGAGE_API_SECRET, SINCH_ENGAGE_REGION, MCP_TOOL_CATEGORIES, MCP_TOOL_MODES. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sinch Engage / MessageMedia's toolset — Messaging, Reporting, Contacts and 1 more — is a fair guide to whether it matches your workflow.
This entry was verified against Sinch Engage / MessageMedia's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Messaging | The Messaging tool exposed by this server. |
| Reporting | The Reporting tool exposed by this server. |
| Contacts | The Contacts tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SINCH_ENGAGE_API_KEY | Credential the server authenticates with. | Yes |
| SINCH_ENGAGE_API_SECRET | Credential the server authenticates with. | Yes |
| SINCH_ENGAGE_REGION | Configuration value read at startup. | Optional |
| MCP_TOOL_CATEGORIES | Configuration value read at startup. | Optional |
| MCP_TOOL_MODES | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.