Skip to main content
Glama
theYahia

Yandex Metrika MCP

by theYahia

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YANDEX_METRIKA_TOKENYesOAuth 2.0 Bearer token from Yandex OAuth

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_countersA

List all Yandex.Metrica counters available to the authenticated user. Returns counter ID, name, site URL, and status. Supports search filtering.

get_counterA

Get full details of a single Yandex.Metrica counter by ID, including configuration, code snippet status, and goals count.

create_counterA

Create a new Yandex.Metrica counter for a website. Returns the new counter ID and tracking code. You need to install the tracking code on the site afterwards.

update_counterA

Update an existing Yandex.Metrica counter — change its name or site URL.

delete_counterA

Permanently delete a Yandex.Metrica counter. This action is irreversible — all historical data for this counter will be lost.

list_goalsA

List all goals configured for a Yandex.Metrica counter. Goals track conversions like page visits, button clicks, or multi-step funnels.

create_goalB

Create a new conversion goal for a counter. Supports types: 'url' (page visit), 'number' (page count threshold), 'step' (multi-step funnel), 'action' (JavaScript event).

delete_goalA

Delete a conversion goal from a counter. Historical goal data in reports is preserved.

export_logsA

Export raw visit or hit logs via the Logs API. Creates a log request and evaluates feasibility. Use source='visits' for session data, source='hits' for pageview data.

get_reportB

Flexible Yandex.Metrica reporting endpoint. Query any combination of metrics (ym:s:visits, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:users, ym:s:newUsers, etc.) with dimensions (ym:s:trafficSource, ym:s:searchEngine, ym:s:country, ym:s:browser, ym:s:deviceCategory, ym:s:date, etc.) over a date range. Supports filters and sorting.

get_report_comparisonA

Compare metrics between two date periods (A vs B). Useful for week-over-week, month-over-month, or campaign before/after analysis.

get_report_drilldownA

Drill down into report data hierarchically. Start at top level, then pass parent_id to explore sub-dimensions (e.g., country -> city, traffic source -> campaign).

get_traffic_summaryA

Quick traffic overview for a counter over a date range. Returns visits, pageviews, unique users, bounce rate, and average visit duration in one call.

get_traffic_sourcesB

Traffic sources breakdown — visits and users by source channel (organic search, direct, social, referral, ad). Quick way to see where traffic comes from.

get_top_pagesA

Top pages by pageviews for a counter. Returns URL, visits, pageviews, bounce rate, and avg duration for each page. Useful for content performance analysis.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theYahia/yandex-metrika-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server