Yandex Tracker MCP vs Git
A side-by-side look at the Yandex Tracker MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Yandex Tracker MCP for support & service management work as a local process; choose Git for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Yandex Tracker MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- 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, TRACKER_ENTITIES_ENABLED. - You want tools like
queues_get_all, queue_get_tags, queue_get_versions.
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Other Tools and Integrations |
| Quality signal | 57/100 · Good | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | TRACKER_TOKENTRACKER_IAM_TOKEN |
Tools & capabilities
Yandex Tracker MCP tools 55
queues_get_allEvery queue the token may see; returns `{values, hits, pages}queue_get_tagsThe tags defined in the queuequeue_get_versionsThe queue's versions, with dates and statusqueue_get_componentsThe queue's components as full objects, with lead, auto-assign flag and `version`; `queue_get_metadata` with `expand: ["components"]` gives ids and names onlyqueue_create_versionCreate a version in the queuequeue_get_fieldsThe fields configured on the queue, local ones included; `schema.required` marks the mandatory onesqueue_get_metadataName, description, default type and priority, plus whatever `expand` asks forcomponent_getOne component with `queue`, `lead`, `assignAuto` and `versioncomponent_createCreate a component in a queuecomponent_updateChange name, description, lead or auto-assign flag; omitted fields keep their value, `clear_lead` removes the leadcomponent_deleteDelete a componentusers_get_allA page of the organization's users; returns `{values, hits, pages}- +43 more on the listing page
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relations
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.
Yandex Tracker MCP
{
"mcpServers": {
"aikts-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",
"TRACKER_ENTITIES_ENABLED": "YOUR_TRACKER_ENTITIES_ENABLED_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Yandex Tracker MCP is categorized under Support & Service Management and uses a local stdio subprocess. Git belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Yandex Tracker MCP for support & service management work and Git for other tools and integrations.
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.
Yandex Tracker MCP is listed as free. Auth: api key required. Git is listed as free. Auth: no auth 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 aikts-yandex-tracker-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yandex Tracker MCP has a quality signal of 57/100 (Good) with 3 views, 0 installs and 122 GitHub stars. Git has 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars.
