Plane MCP Server vs Yandex Tracker MCP
A side-by-side look at the Plane MCP Server and Yandex Tracker MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Plane MCP Server for product management work; choose Yandex Tracker MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Plane MCP Server when
- You need dedicated capabilities in the Product Management domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
PLANE_API_KEY, PLANE_WORKSPACE_SLUG. - You want tools like
project_id, name, description_html.
Choose Yandex Tracker MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRACKER_TOKEN, TRACKER_IAM_TOKEN, TRACKER_SA_KEY_ID, TRACKER_SA_SERVICE_ACCOUNT_ID, TRACKER_SA_PRIVATE_KEY, TRACKER_CLOUD_ORG_ID, TRACKER_ORG_ID. - You want tools like
queues_get_all, fields, page.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 51/100 · Good | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | PLANE_API_KEYPLANE_WORKSPACE_SLUG | TRACKER_TOKENTRACKER_IAM_TOKENTRACKER_SA_KEY_IDTRACKER_SA_SERVICE_ACCOUNT_IDTRACKER_SA_PRIVATE_KEYTRACKER_CLOUD_ORG_IDTRACKER_ORG_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 40 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 80 |
| Full listing | View Plane MCP Server | View Yandex Tracker MCP |
Tools & capabilities
Plane MCP Server tools 4
project_idID of the project to retrievenameTitle of the issuedescription_htmlHTML description of the issue (required by Plane API)issue_idID of the issue to retrieve
Yandex Tracker MCP tools 80
queues_get_allfieldspageper_pageTRACKER_LIMIT_QUEUESqueue_get_tagsqueue_idqueue_get_versionsqueue_create_versionnamedescriptionstart_date- +68 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Plane MCP Server
No confirmed install command for Plane MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Yandex Tracker MCP
{
"mcpServers": {
"yandex-tracker-mcp": {
"command": "uvx",
"args": [
"yandex-tracker-mcp@latest"
],
"env": {
"TRACKER_TOKEN": "YOUR_TRACKER_TOKEN_HERE",
"TRACKER_IAM_TOKEN": "YOUR_TRACKER_IAM_TOKEN_HERE",
"TRACKER_SA_KEY_ID": "YOUR_TRACKER_SA_KEY_ID_HERE",
"TRACKER_SA_SERVICE_ACCOUNT_ID": "YOUR_TRACKER_SA_SERVICE_ACCOUNT_ID_HERE",
"TRACKER_SA_PRIVATE_KEY": "YOUR_TRACKER_SA_PRIVATE_KEY_HERE",
"TRACKER_CLOUD_ORG_ID": "YOUR_TRACKER_CLOUD_ORG_ID_HERE",
"TRACKER_ORG_ID": "YOUR_TRACKER_ORG_ID_HERE"
}
}
}
}
Frequently asked questions
Plane MCP Server is categorized under Product Management and uses an install path we have not confirmed yet. Yandex Tracker MCP belongs to Product Management and uses a local stdio subprocess. Pick Plane MCP Server for product management work and Yandex Tracker MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Plane MCP Server has no confirmed install command yet — follow its own setup instructions.
Plane MCP Server is listed as free. Auth: api key required. Yandex Tracker MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kelvin6365-plane-mcp-server and yandex-tracker-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Plane MCP Server has a quality signal of 51/100 (Good) with 1 views, 0 installs and 40 GitHub stars. Yandex Tracker MCP has 48/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
