
Voice control with Salut (Sber, RU)
Manage posts by voice via Sber's "Salut" assistants (a Russian platform) — using the same actions as the MCP server. Setup details are in the Russian help.
1How it works
The assistant doesn't call the MCP bridge directly — it works through a SmartApp with an HTTPS webhook. The chain:
- 🗣️ you create a "Chat App" smartapp in SmartApp Studio (SberDevices platform);
- 🔗 the assistant recognizes a phrase and POSTs it to your webhook;
- 🤖 the webhook calls the same TestIP actions as MCP (approve, reject, find, schedule a post);
- 📣 it returns text for Salut to speak.
⏱️ Note: the assistant waits at most ~7 seconds for the webhook.
2Easiest way — the ready-made bridge (no coding)
The ready bridge needs no coding — just a token and an address:
- download and unpack voice-bridges.zip;
- set the env vars
TESTIP_API_BASE(your TestIP address) andTESTIP_TOKEN(the project token from step 1); - run it — locally via
node server.mjs(port 8080, webhook path/salute) or on Yandex Cloud Functions (entry pointyandex-cloud-function.handler; one function serves both Salut and Alice); - paste the bridge URL as the smartapp's «Webhook URL» (step 3).
✅ It already replies within 7s and understands Russian commands. See voice-bridges/README.md. The steps below are only if you prefer your own webhook.
3Step 1. Create a project API token
Open «Project info» → «API tokens for AI agents» → «Create token». This is the same token used by the MCP server and the Alice skill — it grants access to this project's posts.
🔒 Copy it once (shown only once) and keep it secret.
4Step 2. Host a bridge webhook
You need an HTTPS endpoint in the SmartApp API format, replying fast (~7s limit).
📥 Incoming: JSON with messageName="MESSAGE_TO_SKILL"; recognized text in payload.message.original_text; sessionId/messageId/uuid at top.
📤 Reply: messageName="ANSWER_TO_USER" with payload.pronounceText (echo sessionId/messageId/uuid).
🤖 Inside, call the same TestIP endpoints as MCP:
GET {BASE}/api/agent/posts?status=draft— find drafts;PATCH {BASE}/api/agent/posts/{id}with{"action":"approve"|"reject"}— approve/reject;POST {BASE}/api/agent/postswith{title,body,scheduledFor}— create a post.
🔒 Header: Authorization: Bearer <token>. Minimal handler:
const q = req.body.payload?.message?.original_text || "";
if (/сколько.*чернов/i.test(q)) {
const r = await fetch(`${BASE}/api/agent/posts?status=draft`, {
headers: { Authorization: `Bearer ${TOKEN}` },
});
const n = (await r.json()).posts.length;
return answer(req.body, `Черновиков: ${n}`);
}
// answer(body, text) формирует ответ платформы:
// { messageName: "ANSWER_TO_USER", sessionId, messageId, uuid,
// payload: { pronounceText: text, pronounceTextType: "application/text" } }5Step 3. Create the SmartApp
- open SberDevices SmartApp Studio (developer.sberdevices.ru);
- create a new «Chat App» smartapp (dialog-only, voice-controlled);
- set its «Webhook URL» to your bridge from step 2 and save.
🗣️ Launch by saying «Салют, запусти <app name>».
6Step 4. Commands (example phrases)
Map phrases to actions in the webhook (by original_text) or via SmartApp Brain intents:
- 🔍 «how many drafts» → find drafts;
- ✅ «approve the latest post» → approve newest draft;
- ⛔ «reject the post about …» → find by text and reject;
- 🗓️ «schedule a post … tomorrow at ten» → create with
scheduledFor.
📣 Keep replies short — Salut reads pronounceText aloud.
7Step 5. Testing, account linking, publishing
Test in the Studio emulator, the Salut app and Sber devices (SberBoom, SberBox, Zvezda).
- 👤 personal use: put the token in the webhook config (one smartapp = one project);
- 🧩 multiple users: set up account linking so each works with their own token/project.
🔒 An unpublished smartapp is private to you — enough for your own channel.
8Security
The token grants access to the project's posts (create, approve, scheduled publish). Basic rules:
- 🔒 keep the webhook and token secret, never log the token;
- 🔗 use HTTPS and reply within 7 seconds;
- 🔁 revoke the token anytime in «Project info» («API tokens» → delete) — the smartapp then stops working.
✅ Voice is handy for approve/reject and status checks; leave risky bulk actions to the dashboard.
Didn't find an answer? Write to us — we'll help.
Contact support