yandex-business-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YBIZ_WORKSPACE | Yes | Path to the workspace directory containing the chain data (ybiz.yaml, data/, feed/). Can also be passed as a `workspace` argument to individual tools or `--workspace` to the CLI. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ybiz_statusB | Сводка по workspace: конфиг сети, число филиалов, есть ли baseline и собранный фид. |
| ybiz_list_branchesC | Список филиалов: company-id, название, адрес, рубрики. |
| ybiz_get_branchB | Полные данные одного филиала (как в data/branches/.yaml). |
| ybiz_update_branchA | Изменить поля филиала. |
| ybiz_add_branchA | Добавить новый филиал. Обязательные поля: company-id, name, address, phone, url, working-time, rubric-id. Формат как у ybiz_get_branch; допустимые ключи — см. README. |
| ybiz_import_exportB | Импорт XML-выгрузки из кабинета Яндекс Бизнеса в YAML-филиалы; сохраняет её как baseline. force=True перезаписывает существующие YAML (локальные несохранённые правки пропадут). |
| ybiz_validateC | Проверка всех филиалов: XSD Яндекса + правила из документации. |
| ybiz_diffC | Что фид изменит относительно baseline: added, removed (будут ЗАКРЫТЫ в Яндексе), changed. |
| ybiz_buildA | Собрать feed/feed.xml. Отказывается, если фид закроет филиалы из baseline, пока их company-id не переданы в allow_close — передавай только по явному подтверждению пользователя. |
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 9 tools
Most tools target distinct resources/actions (list/get/update/add branch, validate, diff, build), so an agent can usually choose correctly. The main ambiguity is ybiz_import_export, whose name suggests bidirectional import/export but whose description only documents importing an XML dump and saving a baseline. ybiz_status and ybiz_validate are related but clearly separated as summary vs actual validation.
All names share the ybiz_ prefix and use snake_case, with clear verb_noun forms for the CRUD operations (list_branches, get_branch, update_branch, add_branch). The pattern is broken slightly by single-word nouns/verbs like status, validate, diff, and the compound import_export, but these still fit the tool's purpose and remain readable.
Nine tools cover the full feed-management workflow without redundancy: inspection, branch CRUD, baseline import, validation, diff preview, and feed build. The count is well-scoped for the stated purpose and every tool earns a place.
The toolset covers the main lifecycle: read/add/update branches, validate, preview changes, and build the feed. There is no explicit delete-branch operation, but removal is indirectly handled through the diff/build flow with allow_close; updating network-level configuration is also not exposed, though it appears to be outside the feed-editing domain.