rush-analytics-mcp

An unofficial MCP server for Rush Analytics: SERP top, Wordstat, suggestions, rank tracking and AI-brand tracking, 14 tools

MCP serverRussian stack

scom-82/rush-analytics-mcpAuthor:scom-82

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/rush-analytics-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio rush-analytics -- npx -y @scom82/rush-analytics-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"rush-analytics","type":"stdio","command":"npx","args":["-y","@scom82/rush-analytics-mcp"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "rush-analytics": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add rush-analytics -- npx -y @scom82/rush-analytics-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.rush-analytics]
command = "npx"
args = ["-y", "@scom82/rush-analytics-mcp"]

If the file already exists, append the block to the end.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "rush-analytics": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "rush-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@scom82/rush-analytics-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

RUSH_ANALYTICS_API_KEYsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 4400e3f.

Text for your agent

Install the server with npx -y @scom82/rush-analytics-mcp, add it to your MCP client with RUSH_ANALYTICS_API_KEY from your Rush Analytics dashboard, then check the balance with rush_balance.

Other ways from the author

npx -y @scom82/rush-analytics-mcp

The recommended README method; the package is published on npm.

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

What it does

The server covers all 38 Rush Analytics API v2 endpoints with fourteen tools: Yandex or Google top-10 SERP parsing, Wordstat frequency, search suggestions, one-shot Fast Positions rank checks, a recurring rank-tracker project (which creates a billed, ongoing monitoring project), indexation checks, Google Keyword Planner data, AI-answer brand tracking, Looker Studio summaries, and project listing. It follows a create-task, check-status, fetch-result pattern, either waiting in-process (up to 540 seconds) or polling manually later.

Who it is for. For SEO specialists with a Rush Analytics account who want the service's full toolset in one MCP server.

Good fit when

You already have a Rush Analytics account and want all its modules from an agent
You need to track brand mentions in AI answers alongside regular SEO
You need a one-off Fast Positions check without starting ongoing monitoring

Not a fit when

You have no Rush Analytics account: without a key only rush_modules and module info work
You only need Wordstat: the full 14-tool set is overkill

Example request

Check example.ru's rankings for ten queries in Yandex via Fast Positions, without starting ongoing monitoring

Limitations

An unofficial project, not affiliated with Rush Analytics. Only 8 of roughly 20 service modules are reachable through the API; the rest (clustering, site audit, text analysis and others) are not exposed by the API. Pro accounts are limited to one concurrent request thread. rush_ranktracker creates a recurring, billed monitoring project, not a one-off check, the README warns about this explicitly.

How to disable. Remove the rush-analytics entry from your MCP client config. If you ran rush_ranktracker, separately stop or delete the monitoring project in the Rush Analytics dashboard.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
RUSH_ANALYTICS_API_KEY secret	Rush Analytics API key; without it only the free rush_modules and reference calls work.
RUSH_ANALYTICS_API_URL	Override for the API base URL.

Security check

rush_ranktracker creates a recurring monitoring project that bills the balance on every scheduled collection
rush_update_ranktracker forces an unscheduled collection that may also bill the balance, the README explicitly warns about this

README in short

The README gives a table of all 14 tools with their balance cost, separately warns that rush_ranktracker and rush_update_ranktracker are billed recurring operations, describes result routing for ranktracker (11 views) and ai-results-tracker (4 views), and links to Rush Analytics' official region and language reference pages.

FAQ

Is rush_ranktracker a one-off check?

No, it creates a recurring project that bills the balance on every scheduled data collection.

Are all Rush Analytics modules available through this server?

No, only 8 of roughly 20, the API simply doesn't expose the rest.

DataLens Skills

Official

Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution

SkillMedium riskRussian stackNo VPN needed12

Yandex Metrika MCP Server

Editors’ pick

A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata

MCP serverMedium riskRussian stackNo VPN needed2

OpenSEO

Official

An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO

MCP serverMedium risk21.5K

Claude SEO

A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents

PluginHigh risk17.9K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

DataLens Skills

Yandex Metrika MCP Server

OpenSEO

Claude SEO