git clone https://github.com/sinch/sinch-mcp-server.git
cd sinch-mcp-server
npm install
npm run build
.template.env
and rename it .env
. Then replace the placeholders with your own credentials and delete any key you don't need. If .env file is not available, create it. The .env
file should look like this ():# Conversation tools related environment variables
CONVERSATION_PROJECT_ID=
CONVERSATION_KEY_ID=
CONVERSATION_KEY_SECRET=
## Optional but recommended: the App ID holding your channels integration configuration. If not set it must be present in the prompt
CONVERSATION_APP_ID=
## Optional, defaults to "us". Other possible values are "eu" and "br"
CONVERSATION_REGION=
## Needed only if you want to send SMS messages: it is the number that will be used as the sender for SMS messages
DEFAULT_SMS_ORIGINATOR=
## Needed only if you want to send location messages: it converts an address to a latitude/longitude pair
GEOCODING_API_KEY=
# Verification tools related environment variables
VERIFICATION_APPLICATION_KEY=
VERIFICATION_APPLICATION_SECRET=
# Voice tools related environment variables (Application key and secret can be the same as for Verification)
VOICE_APPLICATION_KEY=
VOICE_APPLICATION_SECRET=
## Needed only if you want to make calls: it is the number that will be displayed to the user when they receive a call
CALLING_LINE_IDENTIFICATION=
# Mailgun tools related environment variables
MAILGUN_DOMAIN=
MAILGUN_API_KEY=
MAILGUN_SENDER_ADDRESS=
npm run start
By default, this command will start the MCP with all the tools available. If you want to filter the tools that are available in the MCP server, you can use the --tags
option.
For example, if you want to only use the conversation tools, you can modify the command as follows:
# Original command
"start": "tsc && (npx -y supergateway --stdio \"node dist/index.js\" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message)"
# Modified command to only use conversation tools
"start": "tsc && (npx -y supergateway --stdio \"node dist/index.js --tag conversation\" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message)"
You can combine multiple tags by separating them with commas. For example, if you want to use both conversation and verification tools, you can use the following command:
"start": "tsc && (npx -y supergateway --stdio \"node dist/index.js --tag conversation,verification\" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message)"
Configure the MCP server in Claude Desktop. You can then configure the MCP server in the Claude configuration file claude_desktop_config.json with the following script as follows:
{
"mcpServers": {
"sinch": {
"command": "npx",
"args": [
"-y", "supergateway", "--sse", "http://localhost:8000/sse"
]
}
}
}
Note: Replace the http://localhost:8000/sse
with the URL of your MCP server if it is not running locally.
Save the file.
The Sinch MCP server enables customers who build Agentic experiences to easily use Sinch services for communication. The Sinch MCP Server provides AI Assistants such as Claude or code builder such as Cursor or agent builders such as Google, with easy access to various Sinch services including Messaging, Voice, Email and many more.
To get started and to try out the Sinch MCP Server, follow the step by step instructions in our developer blog: Using the Sinch MCP Server.