Yandex 360 (ycli)

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.

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:

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": "..."
      }
    }
  }
}

from ycli.yandex.tracker.client import TrackerClient

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

/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/.

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.

Issues & work items

Agile boards

Dictionaries

Fields, queues & structure

Automation & bulk

Entities, users & search

Pages

Collaboration

Grids (dynamic tables)

Async & uploads

Identity

Surveys & questions

Responses & export

Integrations