SkillFoxx

Yandex Audience MCP

A1 Яндекс Аудитории MCP

Yandex Audience MCP: CRM segments, look-alike audiences, pixels and access management with Yandex login right in chat

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Can irreversibly delete a segment or change someone else's access to it
  • Uploads personal data from a CRM: emails, phone numbers and hashed identifiers
All reasons and checks
Russian stack

a1-x-tech/mcp-yandex-audienceAuthor:A1-x-Tech

Install

Manual install

claude mcp add --transport stdio --scope user yandex-audience -- npx -y mcp-yandex-audience@latest

No token needed in advance; Yandex login happens in chat after connecting.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Can irreversibly delete a segment or change someone else's access to it
  • Uploads personal data from a CRM: emails, phone numbers and hashed identifiers

This is third-party code. Review the repository files before installing.

What it does

The server gives the agent 20 tools for Yandex Audience segments, pixels and access rights. Account connection happens right in the chat via OAuth with PKCE: Yandex sends a one-time code, the token is stored locally with owner-only permissions and refreshes itself. The agent can list segments and pixels with their reach, upload a CRM file with emails, phones or hashed identifiers as a segment in two steps, build a look-alike or pixel-based audience, and grant or revoke a colleague's access. File upload and parameter confirmation are separate steps: processing only starts after an explicit second step. The raw_request tool gives direct access to the remaining API methods for technical operations like restoring a pixel.

Who it is for. For marketers and agencies who build and update Yandex Audience segments for ad campaigns from an agent chat.

Good fit when

  • You want to see which segments and pixels already exist and their status
  • You need to upload a customer list from your CRM as a new segment
  • You need a look-alike audience based on an existing segment, or to grant agency access

Not a fit when

  • You need to manage Yandex Direct campaigns and bids: this server does not touch that
  • Your segment has fewer than 100 records: Audience will not accept it into Direct until it grows
  • You need MD5-hashed data: the API only accepts SHA256

Example request

Upload buyers.csv as a segment called Buyers 2026 and show its parameters before starting processing

MCP

Transport
stdio
Authentication
OAuth

Environment variables

YANDEX_AUDIENCE_TOKEN secret
A ready OAuth token for CI, takes priority over in-chat login
YANDEX_AUDIENCE_OAUTH_CLIENT_ID
Client ID of your own OAuth app instead of the A1-x-Tech app
ASKADS_TELEMETRY
Set to 0 to disable anonymous usage telemetry

Limitations

Segment deletion is irreversible; pixel restoration is only available via raw_request as a separate API method. Minimum 100 records and a maximum of 1 GB per segment. Quotas: 30 requests per second per IP, 5,000 per day per login, and segment create/update capped at 10 per minute, 100 per hour, 500 per day. The server does not merge upload and confirmation into one call and does not auto-retry write operations after a failure.

How to disable. Tell the agent to disconnect Audience, or remove the yandex-audience block from your client config, then revoke access in Yandex ID.

FAQ

Do I need a token in advance?

No, connection happens right in chat via a one-time Yandex OAuth code; a ready token is only needed for CI via the YANDEX_AUDIENCE_TOKEN variable.

What happens when a segment is deleted?

Deletion is irreversible. A pixel can be restored via a separate API method through raw_request.

Discussion

No questions or reviews yet.

All Yandex Audience tools
Editors’ pick

12 dependency-free Yandex Direct tools: a plan-then-confirm write flow, with campaign resume and delete simply not implemented

MCP serverBroad access
Official

The unified LidFly MCP server for Direct, Metrika, Wordstat, VK Ads, Telegram, MAX and Avito with a set of 28 skills

MCP serverBroad access19

LidFly plugins

LidFly Plugin Lapki

Official

The LidFly plugin for Codex and Claude Desktop: Direct, Metrika, Wordstat, Webmaster, VK, Telegram, MAX and Avito in one MCP with 27 skills

PluginBroad access1
Russian stack

An MCP server for Yandex Direct, Metrica, Audiences and Wordstat with read-only mode and change confirmation

MCP serverBroad access50
Russian stack

A paid connector service for Yandex Direct, VK and Avito with analytics, wasted-spend detection and an autopilot layer over the Direct API

MCP serverBroad access4

README in short

The README goes into detail on the in-chat OAuth-with-PKCE flow, a table of what can change data with irreversible actions explicitly flagged, ready instructions for Codex, Claude Code, Claude Desktop, Cursor and VS Code, and a section on anonymous telemetry disabled via ASKADS_TELEMETRY. It separately covers CRM file formats, the 100-record minimum and Yandex Audience API quotas.

README badge

Report a problem