Serve the MCP server¶
ycli mcp start serves every operation as an MCP tool over stdio. It needs the mcp extra
(uv tool install 'yandex-cli[mcp]') and the credentials in its environment.
Choose the tools¶
Serving every tool makes tools/list large, and some hosts cap the number of tools (VS Code
accepts 128). Pick what the session needs:
| Flag | Serves |
|---|---|
--toolsets tracker,wiki |
only those services (tracker, wiki, forms); the default is all |
--toolsets core |
a curated everyday profile of about 40 tools: issues, comments, transitions, worklog, wiki pages and search, form reads |
--tools a,b / --exclude-tools a,b |
add or hide single tools by name; an unknown name fails at start |
--read-only |
no write tools; always wins over the flags above |
--tool-search |
a search tool and a call proxy instead of the tools, for a large set |
status_get and schema_get are always served: the first checks the credentials, the second reads the schema of a body that its tool lists as a free-form object (a body too large to list whole), and the schema of what a tool answers, which no listing carries (tool, then tool and name for a part). To see which tools a set of flags gives without starting the
server:
ycli mcp methods --toolsets core --read-only
Trust the hints¶
Every tool says what it does: reads carry readOnlyHint, writes say whether they are destructive
or idempotent. A host can auto-approve reads and ask before a destructive call. --read-only
removes every write, for a deployment where the agent must not change anything.
A tool that grants access (a role, a permission, an access binding, an embedding) is marked so that a client which honours the mark asks a person on every call, and says so in its description.
Preview a write¶
Every tool that writes takes dry_run. With dry_run: true it sends nothing and answers the
request it would have sent, the same object ycli … --dry-run -o json prints, with secrets masked:
{"dry_run": true, "request": {"method": "PATCH", "url": "https://api.tracker.yandex.net/v3/issues/DE-7", "body": {"summary": "New"}}}
- What the tool reads before its first write is read; the plan is of the first write only. One tool makes several:
wiki_attachments_uploadplans the opening of its upload session. requestisnullwhere the tool would write nothing.- A tool that only reads has no
dry_run: there is nothing to plan, and the argument is refused. The CLI differs:--dry-runis an option of every command, and a read under it goes out. - A tool that grants access prompts for a person on a dry run too: the client decides from the tool, before the server sees the arguments. Where nobody can be asked, plan it with the command:
ycli … --dry-run.
Prompts and resources¶
Besides tools, the server offers a few prompts and resources. A client shows a prompt as a ready request (in Claude Code, /yandex-360:tracker_issue_brief DE-7) and lets you attach a resource to the conversation (@yandex-360:ycli://tracker/issue/DE-7).
| Prompt | What it asks for |
|---|---|
tracker_queue_digest |
the open issues of a queue: how many, what is stuck, who holds what |
tracker_issue_brief |
one issue: where it stands, what was decided, what blocks it |
tracker_sprint_review |
a sprint of a board: what was done, what slipped |
wiki_page_from_issue |
a Wiki page drafted from an issue, created after you approve the draft |
forms_answers_table |
the answers of a form as a table, with a summary |
| Resource | Content |
|---|---|
ycli://tracker/issue/{issue_key} |
the issue, as tracker_issues_get returns it |
ycli://wiki/page/{slug} |
the page's Markdown |
ycli://forms/survey/{survey_id} |
the form's settings, as forms_surveys_get returns them |
ycli://tracker/guide, ycli://wiki/guide, ycli://forms/guide, ycli://guide |
how to work with the service through these tools: the text of the plugin's skills, for a client without the plugin |
A prompt or a resource is offered only when the server serves the tools it is made of: with --read-only there is no wiki_page_from_issue, with --toolsets wiki no Tracker prompt. ycli mcp methods --kind prompts and --kind resources list what a server with the same flags offers. The arguments are in the reference.
Connect a client¶
Most MCP clients take a command and an environment:
{
"mcpServers": {
"yandex-360": {
"command": "uvx",
"args": ["--from", "yandex-cli[mcp]", "ycli", "mcp", "start", "--toolsets", "core"],
"env": {
"YANDEX_ID_OAUTH_TOKEN": "...",
"YANDEX_ID_ORGANIZATION_ID": "..."
}
}
}
}
The exact file and keys for each harness are in Install in your harness. To serve many users over HTTP, see Self-host over HTTP. Every tool and its parameters are in the MCP tools reference.