@theyahia/mts-exolve-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MTS_EXOLVE_TOKEN | Yes | Token for MTS Exolve API. Get it from your MTS Exolve personal account. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsC | Отправить SMS через MTS Exolve. |
| get_sms_statusB | Проверить статус отправленного SMS. |
| make_callB | Инициировать телефонный звонок через MTS Exolve. |
| get_call_statusC | Проверить статус звонка. |
| get_call_recordingC | Получить запись звонка по ID. |
| list_numbersB | Список номеров телефонов на аккаунте. |
| buy_numberB | Купить новый телефонный номер в указанном регионе. |
| send_viber_messageC | Отправить сообщение через Viber. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: SMS vs Viber, call vs SMS, status vs recording. There's no overlap between send_sms, send_viber_message, make_call, or get_call_recording. Even similar pairs like get_sms_status and get_call_status are clearly separated by context.
All tools follow a verb_noun snake_case pattern: send_sms, get_sms_status, make_call, get_call_status, get_call_recording, list_numbers, buy_number, send_viber_message. Verbs are simple and consistent across actions.
With 8 tools, the server covers multiple communication channels (SMS, calls, Viber) and number management without excess. The scope is focused and each tool adds distinct value, fitting the typical 3-15 range perfectly.
The surface covers core SMS and call lifecycles (send/status, make/status/recording), number listing and purchasing, and Viber sending. Minor gaps exist: no Viber status check, no number release/deletion, and no call or SMS history listing, but the essential workflows are functional.