Targetprocess MCP Server vs Yandex Tracker MCP
A side-by-side look at the Targetprocess 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.
T
Targetprocess MCP ServerProduct Management · Local subprocess (stdio)MCP server for Tartget Process52GoodAuth: not declaredVerdict: choose Targetprocess MCP Server for product management work as a local process; 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?
TChoose Targetprocess MCP Server when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_current_releases, get_release_bugs, get_release_features.
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 | T Targetprocess MCP Server | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 52/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | 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 | 8 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 79 | 80 |
| Full listing | View Targetprocess MCP Server | View Yandex Tracker MCP |
Tools & capabilities
Targetprocess MCP Server tools 79
get_current_releasesget_release_bugsget_release_featuresget_release_user_storiesget_release_user_stories_with_descriptionget_release_open_bugsget_release_open_user_storiesget_feature_contentget_feature_commentsget_feature_user_storiesget_not_covered_user_stories_in_featurecovered- +67 more on the listing page
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.
Targetprocess MCP Server
{
"mcpServers": {
"targetprocess-mcp-server": {
"command": "npx",
"args": [
"-y",
"targetprocess-mcp-server"
]
}
}
}
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
Targetprocess MCP Server is categorized under Product Management and uses a local stdio subprocess. Yandex Tracker MCP belongs to Product Management and uses a local stdio subprocess. Pick Targetprocess 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.
Targetprocess MCP Server has no declared pricing — check the project's own site. 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 targetprocess-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, Targetprocess MCP Server has a quality signal of 52/100 (Good) with 0 views, 0 installs and 8 GitHub stars. Yandex Tracker MCP has 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.