Server data from the Official MCP Registry
MCP server for Sber SaluteSpeech API — speech recognition and synthesis.
MCP server for Sber SaluteSpeech API — speech recognition and synthesis.
Valid MCP server (2 strong, 4 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.
12 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: SALUTE_AUTH_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-theyahia-salutespeech-mcp": {
"env": {
"SALUTE_AUTH_KEY": "your-salute-auth-key-here"
},
"args": [
"-y",
"@theyahia/salutespeech-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for Sber SaluteSpeech API — speech recognition (STT) and synthesis (TTS). 5 tools.
Part of Russian API MCP (50 servers) by @theYahia.
{
"mcpServers": {
"salutespeech": {
"command": "npx",
"args": ["-y", "@theyahia/salutespeech-mcp"],
"env": { "SALUTESPEECH_API_KEY": "your-base64-key" }
}
}
}
claude mcp add salutespeech -e SALUTESPEECH_API_KEY=your-key -- npx -y @theyahia/salutespeech-mcp
SALUTESPEECH_API_KEY=your-key npx @theyahia/salutespeech-mcp --http --port=3000
# POST http://localhost:3000/mcp
# GET http://localhost:3000/health
Three options (checked in order):
| Env var | Format |
|---|---|
SALUTESPEECH_API_KEY | Base64-encoded client_id:client_secret |
SALUTE_AUTH_KEY | Same (legacy alias) |
SALUTE_SPEECH_CLIENT_ID + SALUTE_SPEECH_CLIENT_SECRET | Raw credentials (auto-encoded) |
OAuth tokens are obtained and refreshed automatically. The scope defaults to
SALUTE_SPEECH_PERS (individuals); set SALUTE_SPEECH_SCOPE for corporate accounts
(SALUTE_SPEECH_CORP — postpaid, SALUTE_SPEECH_B2B — prepaid).
Get credentials at developers.sber.ru.
| Tool | Description |
|---|---|
recognize_speech | STT from Base64 audio |
synthesize_speech | TTS, returns Base64 audio |
list_models | List recognition models and synthesis voices |
get_task_status | Check async recognition task status |
recognize_file | STT from a local file path |
skill-transcribe — guided workflow for audio transcriptionskill-synthesize — guided workflow for speech synthesisTranscribe the audio file /tmp/meeting.wav
Synthesize "Hello world" with voice Bys_24000 in wav16 format
List available voices
recognize_speech / recognize_file use the synchronous endpoint, capped at
2 MB / 1 minute of audio (larger input returns HTTP 413). For multi-channel audio only
the first channel is recognized. Longer recordings need the asynchronous flow
(data:upload → speech:async_recognize → task:get → data:download) — not yet exposed
as tools; get_task_status covers the polling step.
Synthesis input is capped at 4000 characters (incl. spaces and SSML markup).
self-signed certificate in certificate chain / UNABLE_TO_VERIFY_LEAF_SIGNATURESber's endpoints use the Russian Trusted Root CA (НУЦ Минцифры), which is not in Node.js's default trust store — so the very first OAuth call fails until you trust it.
Fix: download the root CA (russian_trusted_root_ca_pem.crt) from
gosuslugi.ru/crt and point Node at it:
export NODE_EXTRA_CA_CERTS=/path/to/russian_trusted_root_ca_pem.crt
In an MCP client, add it to the server's env block. Do not set
NODE_TLS_REJECT_UNAUTHORIZED=0 in production — it disables TLS verification entirely.
Official guide: SaluteSpeech certificates.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.