This MCP server provides read-only access to Yandex Tracker and Yandex Wiki via MCP-capable clients. It exposes a set of tools that map to Yandex APIs: wiki_page_get, wiki_page_get_by_id, wiki_page_resources_list, wiki_page_grids_list, wiki_grid_get for wiki content and tracker_issue_get, tracker_issue_search, tracker_issue_count, tracker_issue_transitions_list, tracker_queues_list, tracker_issue_comments_list, tracker_issue_attachments_list, tracker_issue_attachment_get, tracker_issue_attachment_preview_get, tracker_queue_get, tracker_user_current, tracker_users_list, tracker_user_get, tracker_issue_links_list, tracker_issue_changelog, and tracker_project_comments_list for tracker data. The server runs in read-only mode, so mutation-like operations are not exposed. Clients should connect to the running binary and communicate over stdio as described in the docs, using the provided tools to fetch data from Yandex services. Exact JSON schemas and validation rules are available via tool introspection at runtime. To start, ensure the environment variables are set and run the server binary with the configured command path. When using clients like Claude Code or IDE integrations, configure the command path to the yandex-mcp binary and provide required environment variables.

Prerequisites:

• Go toolchain is not strictly required to run the server if you use prebuilt binaries, but building from source requires Go installed.
• If building from source, you will need Go 1.19+ and a working Go development environment.

Installation steps (from source):

1. Install Go (if not already installed) from https://golang.org/dl/ or via your OS package manager.
2. Clone the repository: git clone https://github.com/n-r-w/yandex-mcp.git
3. Build the binary: cd yandex-mcp go build -o yandex-mcp ./cmd/yandex-mcp

   Alternatively use a task runner if provided by the project

4. Run the server: ./yandex-mcp

Installation steps (binary releases):

1. Download the appropriate binary release for your OS from the GitHub Releases page: https://github.com/n-r-w/yandex-mcp/releases
2. Extract the archive to your preferred location.
3. Ensure the binary is executable: chmod +x yandex-mcp
4. Run the server: ./yandex-mcp

Configuration:

• Set required environment variable YANDEX_CLOUD_ORG_ID (see environment variables section in the README).
• Optionally configure YANDEX_WIKI_BASE_URL, YANDEX_TRACKER_BASE_URL, YANDEX_IAM_TOKEN_REFRESH_PERIOD, YANDEX_HTTP_TIMEOUT, YANDEX_MCP_ATTACH_EXT, and YANDEX_MCP_ATTACH_VIEW_EXT before starting.

Example run (Linux/macOS): export YANDEX_CLOUD_ORG_ID=your-org-id export YANDEX_WIKI_BASE_URL=https://api.wiki.yandex.net export YANDEX_TRACKER_BASE_URL=https://api.tracker.yandex.net ./yandex-mcp

Note: macOS users may need to adjust security settings to allow the downloaded binary to execute, following prompts similar to the macOS installation notes in the README.

Tips and common issues:

• The server is read-only by design. If you need to perform write-like operations, you would need a different server or a sandbox with explicit permissions.
• IAM tokens for Yandex APIs are refreshed periodically. Ensure yc is installed and configured if your setup requires token refresh via yc iam create-token.
• If you encounter connectivity issues, verify that YANDEX_WIKI_BASE_URL and YANDEX_TRACKER_BASE_URL use https and are reachable from your deployment environment.
• Ensure YANDEX_CLOUD_ORG_ID is accurate; it is required for authorization headers when calling Yandex APIs.
• If using attachments or large payloads, adjust YANDEX_MCP_ATTACH_INLINE_MAX_BYTES and related extension allowlists to suit your security and performance requirements.
• When using IDE integrations, provide the path to the built binary (e.g., bin/yandex-mcp) and set environment variables in the client configuration as shown in the example.
• The MCP tool introspection endpoints will reveal exact JSON schemas and validation rules at runtime; use these to validate client requests and responses.