Productivity · Local MCP server

Yandex 360 (ycli)

Yandex 360 Tracker, Wiki and Forms: read and write tools with honest read-only annotations.

Visit Yandex 360 (ycli)'s website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.bim-ba/ycli
Version
0.56.0
Status
Active
Category
productivity
Transport
stdio (local process)
Package
PyPI, OCI image (Docker)
Published
2026-10-03
Updated
2026-10-03
Publisher
bim-ba (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/bim-ba) · how
Website
github.com/bim-ba/ycli
Repository
github.com/bim-ba/ycli
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
PyPIruntime: uvxyandex-cli0.56.0stdioYANDEX_ID_OAUTH_TOKEN (required, secret), YANDEX_ID_ORGANIZATION_ID (required)
OCI image (Docker)ghcr.io/bim-ba/ycli:0.56.0-stdioYANDEX_ID_OAUTH_TOKEN (required, secret), YANDEX_ID_ORGANIZATION_ID (required)

How to connect Yandex 360 (ycli)

Yandex 360 (ycli) runs locally from a Python package published to PyPI: yandex-cli version 0.56.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx yandex-cli. It reads these environment variables: YANDEX_ID_OAUTH_TOKEN (required, secret) and YANDEX_ID_ORGANIZATION_ID (required); set them in the client's configuration for this server.

Yandex 360 (ycli) runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/bim-ba/ycli:0.56.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e YANDEX_ID_OAUTH_TOKEN -e YANDEX_ID_ORGANIZATION_ID ghcr.io/bim-ba/ycli:0.56.0. It reads these environment variables: YANDEX_ID_OAUTH_TOKEN (required, secret) and YANDEX_ID_ORGANIZATION_ID (required); set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "ycli": {
      "command": "uvx",
      "args": [
        "yandex-cli"
      ],
      "env": {
        "YANDEX_ID_OAUTH_TOKEN": "<secret>",
        "YANDEX_ID_ORGANIZATION_ID": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More productivity servers

All 2,706 →
ServerRunsEndpoint or package
xpay Marketing50+ marketing tools. Lead gen, competitive intel, SEO, content research. Pay-per-use via x402.Remote · HTTPmarketing.mcp.xpay.sh
XposedornotXposedOrNot MCP - free breach-exposure lookup by email.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
xTilesRead and structure notes, projects, tasks, and pages in the xTiles visual workspace.Remote · HTTPLive check: sign-in requiredmcp.xtiles.app
YADE MCP ServerMCP server for YADE - open-source DEM engine. Browse API docs, run simulations, manage tasks.Local · stdioPyPI: yade-mcp
Yandex Audience MCPMCP server for Yandex Audience API: segments (CRM, lookalike, pixel), pixels, grants.Local · stdionpm: mcp-yandex-audience
YAPLDraft-safe project planning: tasks, dependencies, resources, schedules and cost metrics.Remote · HTTPLive check: sign-in requiredmcp.yapl.app
Yardstick ATSManage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.Remote · HTTPLive check: ✓ handshakeapi.yardstick.team
YG3 Marketing MCPMarketing MCP: content, SEO, outbound, LinkedIn, ads. Agents provision a sandbox with one POST.Remote · HTTPLive check: sign-in requiredmcp.yg3.ai