ycli

One Yandex 360 toolkit — four ways to use it. Drive Tracker, Wiki, and Forms from a CLI, an MCP server, a Python SDK, or a Claude Code plugin. Built for AI agents first — pleasant for humans too.

English · Русский

🧩 One SDK, four surfaces — write logic once, use it as a CLI, an MCP server, a Python library, or a Claude Code plugin.
🤖 Agent-native — the MCP server exposes read and write tracker_*, wiki_*, forms_* tools, one per SDK/CLI operation, plus a cross-cutting status tool (counts in Coverage), with honest annotations (reads are marked read-only; writes declare whether they are destructive/idempotent); ycli mcp start --read-only serves a reads-only view for cautious deployments, and --toolsets core serves a curated everyday profile when a host limits how many tools it accepts.
🛡️ Trustworthy — typed pydantic models, the real Yandex API quirks handled for you, and a test suite kept at 100% coverage.
⚡ Zero-friction start — uv add yandex-cli, ycli auth login, go.

The full documentation (tutorial, how-to guides, the CLI, MCP and SDK reference) is at bim-ba.github.io/ycli.

Install

uv add yandex-cli            # CLI + Python SDK
uv add 'yandex-cli[mcp]'     # …plus the MCP server (`ycli mcp start`)

Run it without installing, or install it as a standalone tool:

uvx yandex-cli --help                 # one-off, no install
uv tool install yandex-cli            # persistent CLI
uv tool install 'yandex-cli[mcp]'     # …with the MCP server

pip install yandex-cli works too. The CLI ships as both yandex-cli and the short ycli.

Using an AI harness (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, opencode, Docker)? See Install in your harness.

The SDK's ServiceAccountAuth (IAM tokens minted from a Yandex Cloud service-account key) needs the service-account extra: uv add 'yandex-cli[service-account]'.

Quick start

Pick the surface that fits how you work.

CLI

uv add yandex-cli
ycli --help
ycli tracker issues get TRACKER-1
ycli wiki pages get onboarding

Output formats — a global --format / -o picks how results print (the global options work before or after the subcommand: ycli -o json tracker issues get K = ycli tracker issues get K -o json; a command that declares an option of its own, like forms answers export --format, keeps it):

ycli tracker issues get TRACKER-1            # auto: a pretty table on a TTY…
ycli tracker issues get TRACKER-1 | jq .     # …and raw JSON when piped (agent/script-safe)
ycli -o yaml wiki pages get onboarding       # or: -o json | -o yaml | -o pretty
ycli --jq .summary tracker issues get TRACKER-1   # filter the JSON with jq; a string prints bare

--jq EXPR runs a jq program over the command's JSON result and prints like jq -r: a string comes out raw, anything else as one compact JSON value per line. It cannot be combined with -o yaml / -o pretty, and it needs the jq Python package (a dependency; it has no build for Windows on ARM).

Deleting asks first. A command that destroys data (every delete, clear, abort…) asks DELETE <url> — this deletes data. Continue? on stderr when you are at a terminal, and exits 1 if you decline. In a script, a pipe or CI there is no one to ask, so it fails with exit 2 until you pass --yes / -y: ycli tracker boards delete 7 --yes. Reads and ordinary writes never ask.

Preview a write. --dry-run sends nothing for any write: it prints the request instead (method, URL, body; never your token), through the same -o / --jq output, and exits 0. Reads still run, so a command that reads and then writes shows its first write only: ycli tracker boards delete 7 --dry-run. (The two commands that ask the API itself to validate a request, forms filling submit and wiki pages move, call that --validate-only.)

An endpoint ycli has not wrapped. ycli api PATH --service tracker|wiki|forms calls it like gh api would, with the same auth, retries, output and exit codes:

ycli api issues/TRACKER-1 --service tracker --jq .summary           # GET (the default method)
ycli api issues/TRACKER-1/comments --service tracker -F text=@note.md   # POST: a field turns it into one
ycli api pages/descendants --service wiki -f slug=docs --paginate   # every page, as one JSON array

PATH is relative to the service's base URL; a full URL of a service needs no --service, and any other host is refused (your token never goes elsewhere). -f key=value is a string, -F is typed (true, null, numbers, JSON, @file for a file's text, key[sub]=v to nest, key[]=v for an array); fields of a GET or DELETE go to the query string, otherwise to a JSON body (--input FILE sends a raw body instead). -H 'Name: value' adds a header, -X sets the method, and --dry-run, --yes and --jq behave as everywhere. --paginate follows Tracker's Link: rel="next" and Wiki's next_cursor; Forms pages its listings in more than one way, so pass its paging parameters with -f yourself.

MCP server (read/write)

Run it over stdio (needs the mcp extra):

ycli mcp start               # full read/write tool set (honest annotations)
ycli mcp start --read-only   # reads-only view for cautious deployments

Serving every tool costs a large tools/list and some hosts cap a request (VS Code allows 128 tools), so pick what the session needs:

Flag	Serves
`--toolsets tracker,wiki`	only those services (`tracker`, `wiki`, `forms`); default `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 (unknown names fail at start)
`--read-only`	no write tools; always wins over the flags above
`--tool-search`	lists a search tool and a call proxy instead of the tools; use it with a large set

status_get is always served. The listing omits output schemas and doctest examples (results still carry structuredContent), which cuts tools/list from about 1.9 MB to about 0.5 MB for the full set.

For several users, serve it over HTTP: each MCP client signs its user in through Yandex ID (OAuth), and every tool call runs with that user's own Yandex token. Setup, including the Yandex OAuth app and the reverse proxy, is in Self-host over HTTP.

ycli mcp start --transport http --toolsets core   # needs YCLI__MCP__BASE_URL and an OAuth app

List the tool names a given set of flags exposes without running the server:

ycli mcp methods --toolsets core --read-only

Point an MCP client at it — no prior install needed via uvx (tools are namespaced tracker_*, wiki_*, forms_*):

{
  "mcpServers": {
    "yandex": {
      "command": "uvx",
      "args": ["--from", "yandex-cli[mcp]", "ycli", "mcp", "start"],
      "env": {
        "YANDEX_ID_OAUTH_TOKEN": "...",
        "YANDEX_ID_ORGANIZATION_ID": "..."
      }
    }
  }
}

Python SDK

from ycli.yandex.tracker.client import TrackerClient

tracker = TrackerClient(oauth_token="…", organization_id="…")
issue = tracker.issues.get("TRACKER-1")
print(issue.summary)

Claude Code plugin

/plugin marketplace add bim-ba/ycli
/plugin install yandex-360@ycli

Teaches an agent to drive Yandex 360 through ycli — including the real API quirks. See plugins/yandex-360/.

Skills (Claude Code plugin)

Skill	Use for
`yandex-360`	Entry point — install + auth, pick a surface (CLI/MCP/SDK), route to a domain
`yandex-360-tracker`	Issues, epics, comments, transitions, links, worklog, changelog
`yandex-360-wiki`	Wiki pages, page tree, comments, attachments, YFM authoring
`yandex-360-forms`	Forms, questions/schema, responses, publishing

The skills encode the read/write commands and the gnarly Yandex API quirks (epic-vs-parent, transition discovery, permanent wiki slugs, fields= rules, Forms host/header traps, answers pagination).

Configure

ycli reads two values from the environment (or a .env file — cp .env.example .env):

YANDEX_ID_OAUTH_TOKEN=...        # a Yandex OAuth token with Tracker/Wiki/Forms access
YANDEX_ID_ORGANIZATION_ID=...    # your Yandex 360 organization id

ycli sends the org id as X-Org-Id for every service (HTTP header names are case-insensitive per RFC 9110, so one casing serves all).

Optional settings follow the YCLI__<GROUP>__<SETTING> pattern; ycli rejects an invalid value at startup and names the variable:

Variable	Default	Meaning
`YCLI__HTTP__TIMEOUT_SECONDS`	`30`	Per-request timeout, seconds (> 0)
`YCLI__HTTP__RETRIES`	`3`	Retries for idempotent requests on 429/5xx (≥ 0)
`YCLI__HTTP__MAX_ITEMS`	`500`	Item cap for listings without `--limit`/`--all` (> 0)
`YCLI__LOGGING__LEVEL`	`WARNING`	`DEBUG`, `INFO`, `WARNING`, `ERROR` or `CRITICAL`; `-v` means `INFO` (every HTTP request), `-vv` means `DEBUG`
`YCLI__LOGGING__FORMAT`	`text`	`text` or `json` (one object per line); logs always go to stderr

Get your credentials

Yandex issues OAuth tokens only through a registered application, so it's a one-time app registration plus one command.

1. Register an OAuth app at oauth.yandex.ru and grant it the Tracker, Wiki, and Forms permissions (read and write — the CLI and the MCP server both write; the read scopes alone suffice only if you run the MCP server with ycli mcp start --read-only). Put the ClientID — and the Client secret if you want the headless flow — in your .env (ycli reads it from there):

YANDEX_OAUTH_CLIENT_ID=...        # from your app
YANDEX_OAUTH_CLIENT_SECRET=...    # optional — enables the headless device flow

2. Log in. ycli auth login gets a token, detects your organization, and writes both into .env:

ycli auth login

client id + secret → the device flow: ycli prints a code and a https://ya.ru/device link; approve there and it captures the token — no redirect, works over SSH.
only the client id (or --implicit) → the browser flow: ycli opens the Yandex authorize page; approve, then copy the token it displays and paste it back.

Check it any time with ycli auth status: it shows whose token it is (from Yandex ID), your organization (its name needs the optional directory:read_organization scope; without it you get the id and a note) and whether each service accepts the token. ycli tracker auth status (or wiki, forms) probes just that one service. Both exit non-zero when a service rejects the token.

Prefer to do it by hand?

Headless (device flow):

# 1. start the flow — returns a user_code + verification_url
curl -s -X POST https://oauth.yandex.ru/device/code -d "client_id=$YANDEX_OAUTH_CLIENT_ID"
# 2. open https://ya.ru/device, enter the user_code, approve
# 3. exchange the device_code for the token
curl -s -X POST https://oauth.yandex.ru/token \
  -d grant_type=device_code -d "code=<device_code>" \
  -d "client_id=$YANDEX_OAUTH_CLIENT_ID" -d "client_secret=$YANDEX_OAUTH_CLIENT_SECRET"

Browser (implicit): open https://oauth.yandex.ru/authorize?response_type=token&client_id=<ClientID> in a logged-in browser, approve, and copy the token from the page. (Plain curl can't — implicit needs an interactive browser session.)

Organization id: tracker.yandex.ru/admin/orgs → your organization → copy the identifier.

The Yandex documentation behind each step:

Step	Yandex docs
Register the OAuth app	Registering an app (Yandex ID)
Device flow (`ycli auth login` with a secret)	Entering the code on the authorization page
Browser flow (`--implicit`)	Obtain a token manually
Token and organization header per service	Tracker · Wiki · Forms API access

Exit codes

A failed ycli command exits with a code that says what kind of failure it was, so a script can branch without parsing the message.

Code	Meaning	When
0	ok	the command succeeded
1	failure	any other failure: a 4xx the API rejected, an unmapped error, a declined confirmation
2	usage	a bad command line or an invalid `YCLI__…` setting
3	not found	the API answered 404 (or the token cannot see the object)
4	auth	401 / 403, or no credentials set
5	rate limited	the API answered 429 and the retries ran out (the hint shows `Retry-After`)
6	transient	a 5xx, a timeout or a lost connection: worth retrying later

Coverage

334 operations across 62 resources: Tracker 190, Wiki 58, Forms 86

ycli wraps 334 operations across 62 resources of the Tracker, Wiki, and Forms REST API. Every one is reachable from the Python SDK and the CLI, and 322 MCP tools serve them to agents (321 per service plus status_get).

Legend. ✅ in CLI or MCP means the resource is reachable on that surface; MCP tools carry honest hints (reads are readOnlyHint, writes say whether they are destructive or idempotent), and ycli mcp start --read-only serves only the reads. Resource and operation names link to the official Yandex API reference. A ✅ says ycli wraps the operation; where it differs from what Yandex publishes is listed under Against the published API. Generated from the code by scripts/gen_coverage.py; do not edit by hand.

Tracker

35 resources · 190 operations · 187 MCP tools

Issues & work items

Resource	Operations	CLI	MCP
issues	get · search · count · create · update · move · suggest · scroll_clear	✅	✅
comments	list · get · add · edit · delete · react	✅	✅
links	list · search · add · delete	✅	✅
transitions	list · execute	✅	✅
worklog	list · search · global_list · create · edit · delete	✅	✅
changelog	list	✅	✅
checklists	get · create · edit · delete · clear	✅	✅
attachments	list · download · download_thumbnail · get · delete · upload · upload_temp	✅	✅
remotelinks	list · create · delete	✅	✅

Agile boards

Resource	Operations	CLI	MCP
boards	list · get · create · edit · delete	✅	✅
sprints	list · get · create · edit · delete · start · archive	✅	✅
columns	list · get · create · edit · delete	✅	✅

Dictionaries

Resource	Operations	CLI	MCP
priorities	list · create · edit	✅	✅
statuses	list · create · edit	✅	✅
resolutions	list · create · edit	✅	✅
issuetypes	list · create · edit	✅	✅
linktypes	list	✅	✅

Fields, queues & structure

Resource	Operations	CLI	MCP
fields	list · get · create · edit · category_create · category_edit	✅	✅
localfields	list · get · create · edit	✅	✅
components	list · create · edit · list_for_queue · get · delete · user_permissions · group_permissions	✅	✅
queues	list · get · tags · versions · fields · create · delete · restore · set_permissions · tag_remove · version_create · version_get · version_edit · version_delete · user_permissions · group_permissions	✅	✅
workflows	list · get · for_queue · create · edit · edit_action · delete	✅	✅
projects	list · get · queues · create · edit · delete	✅	✅

Automation & bulk

Resource	Operations	CLI	MCP
macros	list · get · create · edit · delete	✅	✅
triggers	list · get · create · edit · webhook_log	✅	✅
autoactions	get · create · logs · log_detail	✅	✅
dashboards	create · add_cycle_time_widget	✅	✅
bulk	update · move · transition · get · issues	✅	✅
import	task · comment · link · worklog · file · comment_file	✅	✅

Entities, users & search

Resource	Operations	CLI	MCP
entities	create · get · edit · delete · search · history · permissions · set_permissions · direct_permissions · set_direct_permissions · bulk_update · bulk_status · create_report · comments_list · comments_relative · comments_get · comments_create · comments_edit · comments_delete · checklists_create · checklists_edit · checklists_edit_item · checklists_delete · checklists_delete_item · checklists_move · links_list · links_create · links_delete · attachments_list · attachments_get · attachment_download · attachments_attach · attachments_delete	✅	✅
users	get · list	✅	✅
applications	list	✅	✅
filters	get · create · edit · delete	✅	✅
gaps	create · search · delete	✅	✅
me	get	✅	✅

Wiki

11 resources · 58 operations · 56 MCP tools

Pages

Resource	Operations	CLI	MCP
pages	get_by_id · get · descendants · descendants_by_id · grids · create · update · delete · append_content · clone · move · revisions · backlinks	✅	✅
resources	list	✅	✅
recovery	restore	✅	✅
search	query	✅	✅

Collaboration

Resource	Operations	CLI	MCP
comments	list · thread · thread_get · create · delete	✅	✅
attachments	list · get · preview · download · download_by_url · delete · attach · upload	✅	✅
access	create · update · delete · clear	✅	✅

Grids (dynamic tables)

Resource	Operations	CLI	MCP
grids	get · create · update · delete · add_rows · remove_rows · move_rows · add_columns · remove_columns · move_columns · update_cells · clone · suggest_column · update_column · update_row	✅	✅

Async & uploads

Resource	Operations	CLI	MCP
operations	clone_get · gridclone_get · move_get	✅	✅
uploadsessions	create · get · upload_part · finish · abort · abort_all	✅	✅

Identity

Resource	Operations	CLI	MCP
me	get	✅	✅

Forms

16 resources · 86 operations · 78 MCP tools

Surveys & questions

Resource	Operations	CLI	MCP
surveys	list · get · create · modify · delete · publish · unpublish	✅	✅
questions	get · list · create · modify · delete · move	✅	✅
conditions	question_list · question_get · question_create · question_modify · question_delete · question_set_operator · page_list · page_get · page_create · page_modify · page_delete · page_set_operator · submit_list · submit_get · submit_create · submit_modify · submit_delete · submit_set_operator · hook_list · hook_get · hook_create · hook_modify · hook_delete · hook_set_operator	✅	✅
access	get · set · grant · revoke	✅	✅
history	list	✅	✅

Responses & export

Resource	Operations	CLI	MCP
answers	get · list · list_all · export · export_results · download_export · integrations_list · delete · restore	✅	✅
operations	get	✅	✅

Integrations

Resource	Operations	CLI	MCP
hooks	list · get · create · modify · delete	✅	✅
subscriptions	list · get · create · modify · delete · attach	✅	✅
variables	list	✅	✅
notifications	list · get · status_get · restart · cancel · errors_list	✅	✅

Distribution

Resource	Operations	CLI	MCP
keysets	list · get · create · modify · delete · download	✅	✅
filling	get · submit · suggest	✅	✅

Media

Resource	Operations	CLI	MCP
files	upload · verify · download · delete	✅	✅
images	upload · clone	✅	✅

Identity

Resource	Operations	CLI	MCP
me	get	✅	✅

Every resource and operation above deep-links to the Yandex API reference: 318 of 334 operations resolve to their own endpoint page and 15 to their resource's page. No public API reference exists yet for tracker.linktypes, tracker.linktypes.list, shown as plain text. See CONTRIBUTING.md for the intentional exclusions (UI-only endpoints with no public REST API) and per-method notes.

Against the published API

What ycli sends, replayed from its contract tests, compared with what Yandex publishes: the Wiki and Forms OpenAPI documents and Tracker's API reference (prose, so only operations and the query parameters a page lists are compared). A request body is compared only where ycli has a typed model for it and the model is closed; the Bodies compared column says how many that is, so an empty list is not read as a match. The published side is the snapshot in scripts/api_snapshot/; a weekly job fetches it again and opens an issue when Yandex has changed it.

Service	Published	Wrapped	Not wrapped	Operations that differ	Bodies compared	Source
Tracker	190	188	0 (+2 on purpose)	25	—	API reference
Wiki	56	56	0	0	20 of 24	OpenAPI
Forms	84	84	0	17	24 of 30	OpenAPI

Tracker: what differs

Not wrapped on purpose

Operation	Why
`GET /boards`	`boards list` reads the paginated `GET /boards/_paginate`
`GET /users`	`users list` reads the paginated `GET /users/_relative`

Sent by ycli, not published

ycli	Its request
`entities.attachment_download`	`GET /attachments/{file_id}/{filename}`
`linktypes.list`	`GET /linktypes`

Parameters and fields

Operation	ycli	Difference
`POST /bulkchange/_move`	`bulk.move`	query parameters ycli cannot send: `notify`
`POST /bulkchange/_transition`	`bulk.transition`	query parameters ycli cannot send: `notify`
`POST /bulkchange/_update`	`bulk.update`	query parameters ycli cannot send: `notify`
`POST /entities/{entity_type}`	`entities.create`	query parameters ycli cannot send: `fields`
`PATCH /entities/{entity_type}/{entity_ID}`	`entities.edit`	query parameters ycli cannot send: `expand`, `fields`
`POST /entities/{entity_type}/{entity_ID}/attachments/{file_ID}`	`entities.attachments_attach`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`DELETE /entities/{entity_type}/{entity_ID}/checklistItems`	`entities.checklists_delete`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`PATCH /entities/{entity_type}/{entity_ID}/checklistItems`	`entities.checklists_edit`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`POST /entities/{entity_type}/{entity_ID}/checklistItems`	`entities.checklists_create`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`DELETE /entities/{entity_type}/{entity_ID}/checklistItems/{checklist_item_ID}`	`entities.checklists_delete_item`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`PATCH /entities/{entity_type}/{entity_ID}/checklistItems/{checklist_item_ID}`	`entities.checklists_edit_item`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`POST /entities/{entity_type}/{entity_ID}/checklistItems/{checklist_item_ID}/_move`	`entities.checklists_move`	query parameters ycli cannot send: `expand`, `fields`, `notify`, `notifyAuthor`
`POST /entities/{entity_type}/{entity_ID}/comments`	`entities.comments_create`	query parameters ycli cannot send: `expand`, `isAddToFollowers`, `notify`, `notifyAuthor`
`DELETE /entities/{entity_type}/{entity_ID}/comments/{comment_ID}`	`entities.comments_delete`	query parameters ycli cannot send: `notify`, `notifyAuthor`
`PATCH /entities/{entity_type}/{entity_ID}/comments/{comment_ID}`	`entities.comments_edit`	query parameters ycli cannot send: `expand`, `isAddToFollowers`, `notify`, `notifyAuthor`
`GET /entities/{entity_type}/{entity_ID}/events/_relative`	`entities.history`	query parameters ycli cannot send: `direction`, `newEventsOnTop`, `selected`
`POST /issues`	`issues.create`	query parameters ycli cannot send: `notify`
`POST /issues/_search`	`issues.search`	query parameters ycli cannot send: `expand`, `perScroll`, `scrollId`, `scrollTTLMillis`, `scrollType`
`GET /issues/_suggest`	`issues.suggest`	query parameters ycli cannot send: `embed`, `expand`, `fields`, `full`, `queue`
`POST /issues/{id_задачи}/_move`	`issues.move`	query parameters ycli cannot send: `expand`, `initialStatus`, `moveAllFields`, `notify`, `notifyAuthor`
`GET /issues/{issue_ID}`	`issues.get`	query parameters ycli cannot send: `expand`, `fields`
`GET /issues/{issue_ID}/changelog`	`changelog.list`	query parameters ycli cannot send: `field`, `sort`, `type`
`GET /issues/{issue_ID}/comments`	`comments.list`	query parameters ycli cannot send: `expand`
`GET /priorities`	`priorities.list`	query parameters ycli cannot send: `localized`
`GET /queues`	`queues.list`	query parameters ycli cannot send: `expand`

Wiki: what differs

Forms: what differs

Parameters and fields

Operation	ycli	Difference
`GET /answers`	`answers.get`	response fields ycli drops: `started`
`GET /operations/{operation_id}`	`operations.get`	response fields ycli drops: `result`
`GET /surveys`	`surveys.list`	query parameters ycli cannot send: `favourite`, `group`, `name`, `orderby`, `ownership`, `published`, `show_all`
`POST /surveys`	`surveys.create`	body fields ycli cannot send: `api_keys`, `auto_publication`, `captcha`, `file_storage`, `fill_again`, `follow`, `footer`, `iframe`, `metric`, `quiz`, `share`, `show_last_answer`, `stats`, `styles`, `teaser`, `validator_url` body fields ycli sends that are not published: `is_public`, `is_published`, `language` response fields ycli drops: `allow_multiple_answers`, `author`, `auto_publication`, `captcha`, `file_storage`, `fill_again`, `follow`, `followers`, `footer`, `hashed_id`, `iframe`, `max_count`, `metric`, `need_auth`, `quiz`, `share`, `show_last_answer`, `stats`, `styles`, `teaser`, `texts`, `validator_url` model fields that are not published: `modified`
`GET /surveys/{survey_id}`	`surveys.get`	response fields ycli drops: `allow_multiple_answers`, `author`, `auto_publication`, `captcha`, `file_storage`, `fill_again`, `follow`, `followers`, `footer`, `hashed_id`, `iframe`, `max_count`, `metric`, `need_auth`, `quiz`, `share`, `show_last_answer`, `stats`, `styles`, `teaser`, `texts`, `validator_url` model fields that are not published: `modified`
`PATCH /surveys/{survey_id}`	`surveys.modify`	body fields ycli cannot send: `api_keys`, `auto_publication`, `captcha`, `file_storage`, `fill_again`, `follow`, `footer`, `iframe`, `is_favourite`, `metric`, `quiz`, `share`, `show_last_answer`, `stats`, `styles`, `teaser`, `validator_url` body fields ycli sends that are not published: `is_public`, `is_published`, `language` response fields ycli drops: `allow_multiple_answers`, `author`, `auto_publication`, `captcha`, `file_storage`, `fill_again`, `follow`, `followers`, `footer`, `hashed_id`, `iframe`, `max_count`, `metric`, `need_auth`, `quiz`, `share`, `show_last_answer`, `stats`, `styles`, `teaser`, `texts`, `validator_url` model fields that are not published: `modified`
`GET /surveys/{survey_id}/answers`	`answers.list`, `answers.list_all`	query parameters ycli cannot send: `date_from`, `date_to`, `format`, `ordering`, `page_size`, `questions`, `use_slugs`
`POST /surveys/{survey_id}/answers/export`	`answers.export`	response fields ycli drops: `result`
`POST /surveys/{survey_id}/hooks/{hook_id}/subscriptions`	`subscriptions.create`	body fields ycli sends that are not published: `id`
`PATCH /surveys/{survey_id}/hooks/{hook_id}/subscriptions/{subscription_id}`	`subscriptions.modify`	body fields ycli sends that are not published: `id`
`POST /surveys/{survey_id}/questions`	`questions.create`	body fields ycli cannot send: `quiz_comment`, `show_suggest` body fields ycli sends that are not published: `id` response fields ycli drops: `account_id`, `columns`, `conditions`, `data_source`, `fixed`, `header`, `hint_source`, `image`, `items`, `modify_choices`, `multichoice`, `quiz_comment`, `quiz_items`, `rows`, `show_first`, `validators`, `widget`
`DELETE /surveys/{survey_id}/questions/{question_id}`	`questions.delete`	query parameters ycli sends that are not published: `force`
`GET /surveys/{survey_id}/questions/{question_id}`	`questions.get`	query parameters ycli cannot send: `with_slugs` response fields ycli drops: `account_id`, `columns`, `conditions`, `data_source`, `fixed`, `header`, `hint_source`, `image`, `items`, `modify_choices`, `multichoice`, `quiz_comment`, `quiz_items`, `rows`, `show_first`, `validators`, `widget`
`PATCH /surveys/{survey_id}/questions/{question_id}`	`questions.modify`	body fields ycli cannot send: `quiz_comment`, `show_suggest` body fields ycli sends that are not published: `id` response fields ycli drops: `account_id`, `columns`, `conditions`, `data_source`, `fixed`, `header`, `hint_source`, `image`, `items`, `modify_choices`, `multichoice`, `quiz_comment`, `quiz_items`, `rows`, `show_first`, `validators`, `widget`
`GET /surveys/{survey_id}/suggest`	`filling.suggest`	response fields ycli drops: `address`, `avatar`, `board`, `city`, `cloud_uid`, `country_id`, `department`, `display_text`, `email`, `floor_id`, `floor_number`, `full_name`, `group_id`, `login`, `office_id`, `parent_id`, `population`, `queue`, `region`, `role_scope`, `row_id`, `slug`, `status`, `tracks_count`, `type`, `uid`, `url`, `yandex_uid`
`POST /surveys/{survey}/form`	`filling.submit`	response fields ycli drops: `quiz_result` model fields that are not published: `results`, `scores`, `total_scores`
`GET /users/me`	`me.get`	response fields ycli drops: `display`, `login`

Development

uv sync --all-extras   # --all-extras pulls in the `mcp` extra the tests exercise
uv run pytest          # 100% coverage gate; HTTP stubbed with `MockAPI` (no live network)

The source layout and the invariants that keep it regular are in ARCHITECTURE.md; see CONTRIBUTING.md for conventions and how to add an endpoint. Contributions welcome.

License

Metadata

Release files for yandex-cli 0.42.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for yandex-cli 0.42.0
File	Size	Uploaded
yandex_cli-0.42.0.tar.gz	377.4 kB	Oct 3, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for yandex-cli 0.42.0
File	Interpreter	ABI	Platform	Reset
yandex_cli-0.42.0-py3-none-any.whl 558.2 kB Oct 3, 2026	Python 3	none	any	Details

Total release size: 935.5 kB

Release files / yandex_cli-0.42.0.tar.gz

Download URL	yandex_cli-0.42.0.tar.gz
Size	377.4 kB
Tags	Source
SHA-256 checksum How to use checksums	`8b8454e7b5e8ca65d1547e18ba17ec6356469ce6ee307fd48e3672b49fdb0bfd`
BLAKE2b-256 checksum How to use checksums	`537c2761850ae7a4c1c7b5a77de59d9930ea356df062f8c93a4b60045591878e`
Upload date	Oct 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}`

Release files / yandex_cli-0.42.0-py3-none-any.whl

Download URL	yandex_cli-0.42.0-py3-none-any.whl
Size	558.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`d3cf34e1bc22d6e5268c47dad187ef7a45775c78eb567a775afb8149d77594ed`
BLAKE2b-256 checksum How to use checksums	`f79b24c254a3b80462b94225d233e1ee6fccba74bd05bcc41d4a9e712f9b20ff`
Upload date	Oct 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}`