A
licenseNot graded
qualityC
maintenanceMCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.
6 npm
1
MIT
ya360-mcp
by cyxar4uk
Related Servers
Alternatives to ya360-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Node.js MCP server that enables AI assistants to interact with Yandex Tracker task management system through a standardized protocol, supporting operations like creating, updating, and searching issues.433 npm3ISC
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to interact with Yandex 360 organization services, currently supporting Yandex Wiki for reading, editing, and searching pages.49 PyPIMIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to securely interact with Yandex Tracker, supporting issues, queues, comments, worklogs, search, and workflow management with optional Redis caching.571Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to access Yandex Calendar over CalDAV, with the ability to read, create, move, update, and delete events, including recurring events and attendee invitations.1MIT
- AlicenseNot gradedqualityAmaintenanceAn unofficial MCP server that connects AI assistants to Microsoft Planner, enabling natural language task management such as creating tasks, organizing plans, and managing buckets.14MIT
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
yandex_status and yandex_login have clearly distinct purposes: one reports connection/permission state, the other performs OAuth login. The descriptions even cross-reference each other, making misselection unlikely.
Naming Consistency5/5
Both tools follow an identical pattern (yandex_ prefix + a distinct noun/action: status, login). No mixing of conventions or verb styles.
Tool Count3/5
Two tools is thin even for an auth-scoped server, and there is no tooling for anything beyond connect/status. It is defensible for a credentials-only plugin, but feels minimal.
Completeness3/5
Connect and status are covered, but there is no disconnect/logout, token refresh, or any operation on the connected services (Trello/Mail/Calendar data). Agents will hit a dead end after authenticating.
Maintenance
ActivityMaintained
ResponsivenessNo issues