VoteShip vs Yandex Tracker
A side-by-side look at the VoteShip and Yandex Tracker MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose VoteShip for product management work as a local process; choose Yandex Tracker for product management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose VoteShip when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Yandex Tracker when
- You need dedicated capabilities in the Product Management domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TRACKER_TOKEN, TRACKER_ORG_ID. - You want tools like
find_issues, count_issues, create_issue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 43/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | TRACKER_TOKENTRACKER_ORG_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 187 |
| Full listing | View VoteShip | View Yandex Tracker |
Tools & capabilities
VoteShip tools
No tool names declared yet. Check the project README from the listing page.
Yandex Tracker tools 187
find_issuesFind issues in Yandex Tracker. Pass exactly ONE search parameter: "queue" (queue key), "keys" (list of issue keys), "filter" (field->value object), "query" (Tracker query language string, e.g. "Queue: TREK Assignee: me()"), "query2" (query language 2.0 object) or "filterId" (saved filter id). Supports pagination via perPage/page.count_issuesGet the number of issues matching a filter or query.create_issueCreate a new issue in Yandex Tracker. Requires queue key and summary. Text fields support Yandex Flavored Markdown.get_issueGet issue parameters by key or id, e.g. "TREK-123".edit_issueEdit an existing issue (PATCH): only provided fields are changed. For array fields you may pass "add"/"remove"/"set"/"replace" commands via extraFields, e.g. extraFields={"tags": {"add": ["new-tag"]}}.move_issueMove an issue to a different queue. Components, versions and projects are cleared by default (use moveAllFields to keep them). Local fields of the old queue are removed.get_issue_transitionsList workflow transitions available for the issue (with target statuses). Use transition ids with execute_transition.execute_transitionMove an issue to a new status by executing a workflow transition. First get available transitions via get_issue_transitions. Some transitions (e.g. "close") require a resolution via extraFields, e.g. {"resolution": "fixed"}.get_issue_linksList links of an issue (related, dependent, subtask, duplicate, epic links). Pass perPage/page for the paginated variant.release_search_scrollFree scroll-search resources when you stopped paging through a scrolled find_issues result. Body: {"<scrollId>": "<scrollToken>"} for every page you opened.create_issue_linkCreate a link between the current issue and another issue.delete_issue_linkDelete a link between issues by link id (see get_issue_links).- +175 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.
VoteShip
{
"mcpServers": {
"voteship-2": {
"command": "npx",
"args": [
"-y",
"@voteship/cli"
]
}
}
}
Yandex Tracker
{
"mcpServers": {
"yandex-tracker": {
"url": "https://api.tracker.yandex.net/v3"
}
}
}
Frequently asked questions
VoteShip is categorized under Product Management and uses a local stdio subprocess. Yandex Tracker belongs to Product Management and uses a remote HTTP/SSE transport. Pick VoteShip for product management work and Yandex Tracker 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.
VoteShip is listed as free. Auth: no auth required. Yandex Tracker has no declared pricing — check the project's own site. Auth: api key required. 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 voteship-2 and yandex-tracker as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, VoteShip has a quality signal of 43/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Yandex Tracker has 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars.