MCP.so
登录
Y

Yandex Tracker MCP Server

@aikts

基本信息

分类

其他

传输方式

stdio

作者

aikts

提交者

Igor Latkin

关于 Yandex Tracker MCP Server

Enable AI assistants to securely access and manage Yandex Tracker issues, queues, users, and related data through a comprehensive MCP server. Perform advanced searches, retrieve detailed issue information, and manage queues with optional caching for improved performance. Integrat

#yandex#yandex-tracker#python

Yandex Tracker MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "yandex-tracker": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TRACKER_TOKEN",
        "-e",
        "TRACKER_CLOUD_ORG_ID",
        "-e",
        "TRACKER_ORG_ID",
        "ghcr.io/aikts/yandex-tracker-mcp:latest"
      ],
      "env": {
        "TRACKER_TOKEN": "your_tracker_token_here",
        "TRACKER_CLOUD_ORG_ID": "your_cloud_org_id_here",
        "TRACKER_ORG_ID": "your_org_id_here"
      }
    }
  }
}

Yandex Tracker MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Yandex Tracker Mcp Server?

A Model Context Protocol (MCP) server that provides AI assistants with secure, authenticated access to Yandex Tracker APIs—including issues, queues, comments, worklogs, and search—with optional Redis caching for performance.

How to use Yandex Tracker Mcp Server?

Set the required environment variables (TRACKER_TOKEN and either TRACKER_CLOUD_ORG_ID or TRACKER_ORG_ID). Optionally configure transports (stdio, streamable-http, or SSE), queue restrictions, and Redis caching. The server exposes MCP tools such as queues_get_all, issue_get, and issues_find.

Key features of Yandex Tracker Mcp Server

  • Complete Queue Management with pagination and tag retrieval
  • User account information and organizational data access
  • Issue operations: details, comments, links, worklogs, attachments
  • Advanced Query Language for complex filtering and sorting
  • Optional Redis caching for improved response times
  • Configurable queue access restrictions for security

Use cases of Yandex Tracker Mcp Server

  • Retrieve and display all queues, their tags, versions, and local fields
  • Fetch detailed issue information, comments, and attachments
  • Search and count issues using Yandex Tracker Query Language
  • Manage worklog entries and related issue links for time tracking

常见问题

1

What environment variables are required?

A Yandex Tracker OAuth token (`TRACKER_TOKEN`) and one organization ID (`TRACKER_CLOUD_ORG_ID` or `TRACKER_ORG_ID`) are required.

2

Can I restrict which queues the server can access?

Yes, by setting `TRACKER_LIMIT_QUEUES` to a comma-separated list of queue keys; all tools respect this restriction.

3

What transport options are supported?

Stdio, streamable-http, and SSE transports are available via the `TRANSPORT` environment variable.

4

Where does cached data live?

Optional Redis caching is configured with `CACHE_ENABLED`, `CACHE_REDIS_ENDPOINT`, `CACHE_REDIS_PORT`, and `CACHE_REDIS_DB`.

5

Is there a limit on how many issues a search can return?

Yes, the `issues_find` tool returns up to 500 issues per page.

评论

其他 分类下的更多 MCP 服务器