home / mcp / yatracker mcp server
Provides MCP access to YaTracker (Yandex Tracker) data via HTTP and CLI operations to manage issues, comments, transitions, and attachments.
Configuration
View docs{
"mcpServers": {
"belkin-digital-yatracker-connector": {
"url": "http://localhost:8080/sse",
"headers": {
"YATRACKER_TOKEN": "your_oauth_token_here",
"YATRACKER_ORG_ID": "7579907"
}
}
}
}You can run YaTracker Connector as an MCP server to interact with the Yandex Tracker API from an MCP client. It supports a Docker-based quick start and a local Python setup, exposing a set of tasks, comments, transitions, attachments, and metadata through a structured MCP interface.
You connect to the MCP server from your MCP client using the configured endpoint. For remote interactions, you typically reference the HTTP endpoint, while for local, self-contained setups you run the server locally and point your MCP client to the local URL. The available operations let you search and list issues, read and add comments, manage transitions, handle attachments, and access queue metadata. Use the client to list issues in a queue, fetch details for a specific issue, update fields, add comments or attachments, and download attachments. You can also list queues, fields, and workflows to understand how work items are modeled in your Yandex Tracker instance.
To start quickly, choose Docker for a straightforward setup, then configure credentials in the environment file and bring the stack up. If you prefer a local Python setup, install dependencies, create the environment file, and run the CLI-based server locally. The MCP server exposes an endpoint suitable for standard MCP clients, and you can configure the client to connect via the provided URL.
Prerequisites you need before installing: Docker (optional but recommended), Python 3.11 or newer, and access to a Yandex Tracker API token with your Organization ID.
Option 1 — Docker (recommended) 1. Create an environment file from the sample 2. Edit the file to include your credentials 3. Start the services with Docker Compose 4. The MCP server will be available on port 8080.
# 1. Create .env from the sample
cp config/sample.env .env
# Edit .env to add credentials like YATRACKER_TOKEN and YATRACKER_ORG_ID
# 2. Run the stack
docker-compose up -dPrerequisites and credentials you will configure in the environment file include the Yandex Tracker API token and your organization ID. The sample environment file shows the required variables you must set.
Option 2 — Local installation 1. Install dependencies 2. Create the environment file 3. Use the CLI to start and interact with the server
# 1. Install dependencies
pip install -r requirements.txt
# 2. Create environment file
cp config/sample.env .env
# Add YATRACKER_TOKEN and YATRACKER_ORG_ID
# 3. Run via CLI
PYTHONPATH=src python3.11 -m scripts.cli issues list --queue CRMIf you are wiring a Claude Code MCP client, configure the MCP server endpoint as shown.
{
"mcpServers": {
"yatracker": {
"transport": "sse",
"url": "http://localhost:8080/sse"
}
}
}Search and list issues across queues with filters and limits.
Retrieve detailed information for a specific issue by key.
Create a new issue or lead in a specified queue.
Update fields on an existing issue.
List comments for a given issue.
Add a new comment to an issue.
Add a comment together with an attachment to an issue.
List available status transitions for an issue.
Execute a status transition on an issue.
Download attachments from an issue.
Attach a file to an issue.
List all available queues.
List fields for a specific queue.
List all system fields.
List issue types for a queue.
Get the workflow graph for a queue.