Laraue Boards vs Yandex Tracker
A side-by-side look at the Laraue Boards and Yandex Tracker MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Y
Yandex TrackerProduct Management · Local subprocess (stdio)MCP server for Yandex Tracker: full API v3 coverage (187 tools)44FairAuth: api key requiredVerdict: choose Laraue Boards for product management work; choose Yandex Tracker 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 Laraue Boards when
- You need dedicated capabilities in the Product Management domain.
YChoose Yandex Tracker when
- You need dedicated capabilities in the Product 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_ORG_ID.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Y Yandex Tracker | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 33/100 · Emerging | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TRACKER_TOKENTRACKER_ORG_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Laraue Boards | View Yandex Tracker |
Tools & capabilities
Laraue Boards tools
No tool names declared yet. Check the project README from the listing page.
Yandex Tracker tools
No tool names declared yet. Check the project README from 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.
Laraue Boards
No confirmed install command for Laraue Boards yet — follow the setup steps linked from its listing page rather than a guessed package name.
Yandex Tracker
{
"mcpServers": {
"yandex-tracker": {
"command": "npx",
"args": [
"-y",
"tracker-mcp"
],
"env": {
"TRACKER_TOKEN": "YOUR_TRACKER_TOKEN_HERE",
"TRACKER_ORG_ID": "YOUR_TRACKER_ORG_ID_HERE"
}
}
}
}
Frequently asked questions
Laraue Boards is categorized under Product Management and uses an install path we have not confirmed yet. Yandex Tracker belongs to Product Management and uses a local stdio subprocess. Pick Laraue Boards 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. Laraue Boards has no confirmed install command yet — follow its own setup instructions.
Laraue Boards has no declared pricing — check the project's own site. 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 laraue-boards-2 and yandex-tracker as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Laraue Boards has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Yandex Tracker has 44/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.