Sinch MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILGUN_DOMAIN | No | Mailgun domain from the Mailgun / Domains section of the Mailgun dashboard | |
| MAILGUN_API_KEY | No | Mailgun API key from the Mailgun / Domains section of the Mailgun dashboard | |
| NGROK_AUTH_TOKEN | No | If you want to use the tool get-message-events, you have to be able to receive events related to a message. If this variable is set, the MCP server will open a tunnel to your local machine using ngrok | |
| GEOCODING_API_KEY | No | Your Google Geocoding API key if you want to use the location feature. This is needed to convert an address to a latitude/longitude pair | |
| CONVERSATION_APP_ID | No | This is the ID of the conversation app you want to use. You can find it in the Conversation API / Apps section of the Sinch Build dashboard. If you don't set it, you will have to specify it in the prompt | |
| CONVERSATION_KEY_ID | No | Select or create a new access key in the Access keys section of the Sinch Build dashboard | |
| CONVERSATION_REGION | No | This is the region where your conversation app and templates are located. It can be us, eu, or br. If you don't set it, it defaults to us | us |
| VOICE_APPLICATION_KEY | No | Voice API application key from the Voice / Apps section of the Sinch Build dashboard | |
| DEFAULT_SMS_ORIGINATOR | No | The phone number that will be used as the sender for SMS messages. Depending on your country, this setting may be required | |
| MAILGUN_SENDER_ADDRESS | No | Mailgun sender address for sending emails | |
| CONVERSATION_KEY_SECRET | No | This is the secret associated with the Access Key you selected or created | |
| CONVERSATION_PROJECT_ID | No | Select the project you want to use from your Sinch Build dashboard | |
| VOICE_APPLICATION_SECRET | No | Voice API application secret from the Voice / Apps section of the Sinch Build dashboard | |
| CALLING_LINE_IDENTIFICATION | No | The phone number that will be displayed to the user when they receive a call | |
| VERIFICATION_APPLICATION_KEY | No | Verification API application key from the Verification / Apps section of the Sinch Build dashboard | |
| VERIFICATION_APPLICATION_SECRET | No | Verification API application secret from the Verification / Apps section of the Sinch Build dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sinch-mcp-configurationA | This tool allows you to retrieve the configuration of the Sinch MCP server. It provides information about which tools are enabled and disabled with some troubleshooting information about why a tool would be disabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| conversation-app-id |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose described in its name and description.
The single tool name follows a consistent pattern of 'sinch-mcp-configuration', which is descriptive and aligns with the server's purpose. There are no other tools to compare against, so consistency is inherently perfect.
A single tool for a server named 'Sinch MCP Server' suggests a very limited scope. While it might be appropriate for a minimal configuration server, it feels thin and underdeveloped for a general-purpose server, indicating potential gaps in functionality.
The tool only provides configuration retrieval, which is a meta-operation about the server itself. There are no tools for actual Sinch-related operations (e.g., sending messages, managing contacts), making the surface severely incomplete for any practical use case beyond server introspection.