← All help topics

Voice control with Alice (RU)

Manage posts by voice via Yandex Alice (a Russian assistant) — using the same tools as the MCP server. Setup details are in the Russian help.

1How it works

Alice doesn't call the MCP server directly: MCP is stdio, while Alice needs an HTTPS webhook. A small bridge sits in between:

  • 🗣️ an Alice skill (Yandex Dialogs) sends the recognized phrase to your webhook
  • 🔁 the webhook calls the same TestIP actions as MCP (approve/reject/find/schedule) via the project API
  • 🔊 and returns text for Alice to speak

So Alice manages posts with the same tools as MCP, just over an HTTP bridge.

2Easiest way — the ready-made bridge (no coding)

Download and deploy the ready bridge without any coding: voice-bridges.zip, then unzip it.

  1. Set TESTIP_API_BASE (your TestIP address) and TESTIP_TOKEN (the project token from step 1).
  2. Run the bridge: locally with node server.mjs (port 8080, webhook path /alice) or deploy to Yandex Cloud Functions (entry point yandex-cloud-function.handler, free tier; one function serves both Alice and Salut).
  3. Paste the bridge URL as the skill's Webhook URL (step 3).

Russian commands are built in (how many drafts, approve/reject latest, create draft, help). See voice-bridges/README.md. The steps below are only if you prefer to write your own webhook.

3Step 1. Create a project API token

Path: «Информация о проекте» → «API-токены для AI-агентов» → «Создать токен». This is the same token used by the MCP server and gives access to this project's posts.

  • ⏱️ copy it once (shown only once)
  • 🔒 keep it secret, like a password

4Step 2. Host a bridge webhook

You need an HTTPS endpoint that accepts Yandex Dialogs requests (JSON with request.command) and returns { response: { text, end_session } }. It maps phrases to TestIP API calls with your token — the same 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/posts with {title,body,scheduledFor} — schedule

Header: Authorization: Bearer <token>. Yandex Cloud Functions (free tier) or any Node host works. Minimal handler:

const q = req.body.request.command;
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 reply(`Черновиков: ${n}`);
}

5Step 3. Create the Alice skill

Open dialogs.yandex.ru/developer and create a skill:

  1. Create a dialog → «Навык в Алисе».
  2. Set the name and activation phrase.
  3. Settings → Backend → Webhook URL: put your bridge URL from step 2.
  4. Save and test in the console.

6Step 4. Commands (example phrases)

Map phrases to actions in the webhook:

  • 📊 "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 10" → create with scheduledFor

Keep replies short — Alice reads text aloud. Draft complex posts in the dashboard; use voice to approve/reject and ask for status.

7Step 5. Account linking and privacy

  • 👤 Personal use: just put the token in the webhook config (one skill = one project).
  • 🧩 Multiple users: set up account linking (OAuth) in Dialogs so each user uses their own token/project.
  • 🔒 Privacy: an unpublished skill is private to you — enough for your own channel. Publishing to the Alice catalog is optional.

8Security

The token grants access to the project's posts (create, approve, scheduled publish), so:

  • 🔒 keep the webhook and token secret, use HTTPS, never log the token
  • 🔁 revoke the token anytime in the dashboard («API-токены» → delete) — the skill stops working immediately
  • 🎙️ voice is best for approve/reject and status; leave risky bulk actions to the dashboard

Didn't find an answer? Write to us — we'll help.

Contact support