Skip to main content
Glama
Sign In
fall-out-bug

yandex-mcp

by fall-out-bug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Archived — superseded by aikts/yandex-tracker-mcp

This repository is archived. Do not use it.

After reading the code of existing Yandex Tracker MCP servers (not just their READMEs), we found aikts/yandex-tracker-mcp is a mature superset of everything built here:

  • Standalone per-user OAuth profile — the same MCP-SDK OAuthAuthorizationServerProvider architecture (authorize → Yandex, callback, server-side code exchange, no token passthrough, refresh+rotation+revoke, DCR, RFC 8707), with redis/memory/encrypted stores. (Our packages/tracker-mcp/src/auth/* was a less-mature duplicate.)

  • Gateway / reverse-proxy Bearer passthrough — reads a per-user Yandex token from Authorization: Bearer for deployments where a gateway (e.g. Faust) holds the tokens. Same as our v0.1 HTTP bearer mode.

  • Plus IAM tokens, service-account auth, both X-Org-ID / X-Cloud-Org-ID, caching, a wide tool surface, elicitation confirmations.

  • Apache-2.0, Python (Python is also the language of our agent runtime, Gena).

Per the decision gate (reuse established OSS rather than maintain a duplicate), we adopt aikts and retire this repo.

What carries over (verified here, still valid for aikts)

These facts were verified while building this repo and apply equally to aikts / Tracker v3:

  • Tracker OAuth scopes: cloud:auth + tracker:read + tracker:write (cloud:auth is the one that unblocks Cloud-org access; without it Tracker returns 401 even with the tracker scopes).

  • Cloud-org auth: Authorization: OAuth <token> + X-Cloud-Org-Id: <org-id> — direct OAuth, no IAM exchange (the OAuth→IAM exchange is dead for federated Cloud users on tokens issued after 2026-06-01).

  • Tracker v3 search body is top-level {query}; perPage/page are query params.

Related MCP server: Vault MCP

Reusable dev helpers (not server-specific)

These three scripts in this repo work for any Yandex Tracker OAuth setup:

  • scripts/fetch-token.ts — local OAuth code-flow helper to obtain a Tracker access token (run the dance once).

  • scripts/discover-org.ts — non-admin Cloud-org id discovery via IAM.

  • packages/tracker-mcp/scripts/live-probe.ts — spawn any stdio Tracker MCP and call get_myself / search_issues live to verify it works.

Keep them as references; they are not published as a package.

This server cannot be deployed

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Access

    Scottpedia0
    A
    license
    Not graded
    quality
    C
    maintenance
    Self-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.
    125 npm
    MIT

  • Vault MCP

    Zerocreds-com
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables LLM agents to securely use credentials like passwords and API keys without exposing them in the context window, through encrypted storage and proxy-based injection.
    1 npm
    3
    MIT

  • AI Service Gateway MCP

    Yormede
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to securely access authenticated services (HTTP, SSH, SMTP) without exposing secrets, by acting as a server-side proxy that injects authentication.
    MIT

  • grantd-mcp

    rafavecchi
    A
    license
    Not graded
    quality
    D
    maintenance
    OAuth token broker for AI agents to securely act on a user's behalf across third-party APIs (Gmail, Slack, GitHub, Notion, etc.) by vaulting tokens server-side and never exposing them to the LLM.
    1
    MIT