ya360-mcp: Yandex Tracker, Mail and Calendar in Claude
ya360-mcp
An unofficial MCP server and Claude Code plugin with 45 Yandex 360 tools and 11 ready workflows such as standup and weekly report
- 7 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server reads Yandex mail, calendar and issues and, with write permissions granted, sends mail and edits events and issues
- Yandex tokens are kept on the computer in the system storage or in environment variables
Install
- Works in
- Services
Manual install
/plugin marketplace add cyxar4uk/ya360-mcpAdds the plugin marketplace to Claude Code.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server reads Yandex mail, calendar and issues and, with write permissions granted, sends mail and edits events and issues
- Yandex tokens are kept on the computer in the system storage or in environment variables
This is third-party code. Review the repository files before installing.
What it does
The Node.js server runs on the user's computer and talks to Yandex directly, with no intermediary. Sign-in is a Sign in with Yandex button in the browser, and tokens go to the system secure storage. The tools cover Tracker (issues, comments, links, attachments, time tracking, sprints and boards), Mail (search, reading without marking as read, drafts, sending, moving) and Calendar (events with recurrence, creating and editing). The plugin adds workflows: standup, Telemost meeting recap with issue creation, meeting prep, weekly report, mail to issue, stale issues, sprint planning and review.
Who it is for. Team leads and developers who track work in Yandex Tracker, use Yandex Mail and Calendar, and work in Claude Code or Claude Desktop.
Good fit when
- You want a standup or weekly report assembled from Tracker and Calendar
- After a Telemost meeting you want issues with assignees and due dates created
- You want emails turned into Tracker issues without duplicates
- You want control: the agent reads mail and calendar, and writing is switched on by separate permission groups
Not a fit when
- You use claude.ai in a browser or the mobile app: local servers do not start there
- Your organization allows only its own OAuth apps, so the shared sign-in will not work without setup
- You need an official Yandex server: the project is not affiliated with Yandex
Example request
Process yesterday's Telemost meeting and create Tracker issues after I confirmMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
YANDEX_MCP_READONLY- 1 keeps read-only access regardless of granted permissions
Limitations
The project is unofficial and not affiliated with Yandex. It runs only on the user's computer: Node.js 20 or newer is required, and local servers do not start in browser claude.ai or the mobile apps. Access is read-only by default, with writing, sending and deleting enabled by permission groups. Tracker needs an organization ID. Six stars, one author, last commit in September 2026. Workflow instructions are written in Russian, and Claude replies in the user's language. In Claude Desktop the workflows live in the plus menu; in Claude Code commands carry the ya360 prefix, and workflows without a prefix are installed with a separate command.
How to disable. Set YANDEX_MCP_READONLY=1, then run ya360-mcp logout or remove the plugin with /plugin uninstall ya360, and revoke the app access in Yandex ID.
FAQ
Can the server be limited to reading?
Yes, access is read-only by default, and YANDEX_MCP_READONLY=1 keeps it read-only even if write permissions are granted.
Do I need my own OAuth app?
Usually not, sign-in goes through Sign in with Yandex. Your own app on oauth.yandex.ru is needed if the organization allows only its own.
Where does the server run?
Only on the user's computer, in Claude Code, Claude Desktop and Cowork sessions on that computer.
How many tools does the server have?
Forty-five tools across Tracker, Mail and Calendar, with the full list in the repository wiki.
Which workflows does the plugin add?
Eleven, including standup, meeting recap, meeting prep, weekly report, mail to issue and sprint planning.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker MCP with one-click install
yandex-tracker-mcp
A Yandex Tracker MCP server with a .mcpb extension for Claude Desktop that needs no terminal: issues, comments, status transitions and a read-only mode
Yandex Calendar MCP server
Яндекс Календарь MCP для Claude
An MCP server for Yandex Calendar: view, create and delete events using an app password
Yandex Tracker MCP in Go: 180 tools with access modes
mcp-yandex-tracker
A Go server with the widest tool set for Yandex Tracker: issues, boards, sprints and worklogs, with read-only and full modes
Yandex Tracker MCP with 146 tools
ya-tracker-mcp
Full Yandex Tracker API coverage via uvx: 146 tools for issues, projects, portfolios, goals, boards, sprints and worklogs
Yandex Tracker MCP with a report scheduler
Yandex Tracker MCP
A Python Yandex Tracker MCP server with issues, a recurring report scheduler and a SQLite run history
yandex-tracker-mcp: Tracker issues, checklists and time tracking
yandex-tracker-mcp
An independent Python MCP server for the Yandex Tracker REST API v3: issues, transitions, checklists, worklogs and time reports
README in short
The README, in English and Russian, covers capabilities by area, 11 workflows, installation as a plugin, a .mcpb extension or manually, permissions, configuration and example prompts, with a detailed Russian wiki.