Sinch MCP server

What the model can do

Sinch Conversation API (SMS, RCS, WhatsApp, Viber, Messenger and other channels): the project's apps and channels, message history by app, contact, conversation, channel, direction and time (who, when and which channel, never the text or phone numbers), conversations and the most recent ones, and contacts looked up by external id or phone number; when you ask, can send a text message to a contact or number (costs money per message), create, merge or delete a contact, stop or delete a conversation, and delete a message.

Reads

• sinch_appsThe Sinch project's Conversation API apps: id, name, processing mode and the channels each has configured (channel names only…
• sinch_messagesSinch message history, newest first: each message's id, direction (TO_APP from a contact, TO_CONTACT sent by the app), channel, kind (text, media…
• sinch_conversationsSinch conversations for an app or a contact: id, contact, whether active, the active channel and when a message was last received.
• sinch_recent_conversationsAn app's Sinch conversations with the most recent message first: each conversation and its last message's direction, channel, kind and time…
• sinch_contactsSinch contacts: look one up by your own external id, or by a channel and identity such as SMS and a phone number in E.164 (used to search…
• sinch_contactOne Sinch contact by id: external id, language, channels and channel priority.

Acts, when you ask

These change something in Sinch. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• sinch_send_messageSends a text message through Sinch to one recipient outside the company — an existing contact…
• sinch_create_contactCreates a Sinch contact with one or more channel identities (e.g. SMS and a phone number) and a language; nobody is messaged.
• sinch_merge_contactsMerges one Sinch contact into another: the source contact's identities and conversations move to the destination and the source contact is removed…
• sinch_delete_contactPermanently deletes a Sinch contact.
• sinch_stop_conversationStops an active Sinch conversation; the next message to or from the contact starts a new one.
• sinch_delete_conversationPermanently deletes a Sinch conversation and all its messages from Sinch's history.
• sinch_delete_messagePermanently deletes one message from Sinch's history (it does not unsend a delivered message).

Connect it

First connect Sinch on Dashboard → Connections, then add Memtro to your client once. The Sinch tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Sinch connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who messaged us on WhatsApp today?
• › Which conversations had a message in the last hour?
• › How many messages did we send by SMS this week?
• › Which channels does our support app have configured?
• › Send an SMS to +447700900123 saying the engineer is on the way.

Questions

Is this an official Sinch MCP server?

No. It is Memtro's MCP server with Memtro's Sinch connector behind it: the connector reads Sinch through its API with the credentials you connect on Dashboard → Connections, and Sinch publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Sinch?

Only when you ask, and only what it has been granted: send a text message to a contact or phone number (spends Sinch credit); create a contact; merge two contacts (the source contact is removed); delete a contact; stop an active conversation; delete a conversation and its messages; delete a message. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server