Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

SEO Tools: A-Parser bridge

by antohinsversion 1.8.0i★ 8 (Stars for the whole repo)iRuns on your computerRepository ↗
Registry nameio.github.antohins/seo-tools-mcp-aparser

How to install

What it does

Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only).

  • Connects Runs on your computer
  • Account or key Needs APARSER_PASSWORD
  • Category Marketing & social media

Use together with

Skills that teach the AI this kind of work; they work alongside this one

scroll-world

A skill that turn any brand into a scrollable 3D world landing page

by oso95★ 11,0551 skills

Skill · How-to guide

social-auto-upload

自动化上传视频到社交媒体:抖音、小红书、视频号、tiktok、youtube、bilibili

by dreammis★ 16,657 (whole repo)4 skills

Skill · How-to guide

native-subtitle-quote-image

保留视频内嵌字幕,精确取帧并生成 3:4 社交长图的 Agent Skill

by chengyi-ai★ 2,8881 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install SEO Tools: A-Parser bridge. Follow https://mcp.popnx.com/i/antohins-seo-tools-mcp-aparser.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SEO Tools: A-Parser bridge for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "seo-tools-aparser": { "command": "npx", "args": [ "-y", "seo-tools-mcp-aparser" ], "env": { "APARSER_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For APARSER_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SEO Tools: A-Parser bridge tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SEO Tools: A-Parser bridge key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SEO Tools: A-Parser bridge site ↗

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "seo-tools-aparser": {
          "command": "npx",
          "args": [
            "-y",
            "seo-tools-mcp-aparser"
          ],
          "env": {
            "APARSER_PASSWORD": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use SEO Tools: A-Parser bridge and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using SEO Tools: A-Parser bridge or shows a SEO Tools: A-Parser bridge tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • APARSER_URL A-Parser API endpoint, e.g. http://IP:9091/API (Settings -> API).
  • APARSER_GOOGLE_PRESET Default config preset for SE::Google (preset name from the GUI).
  • APARSER_YANDEX_PRESET Default config preset for SE::Yandex (preset name from the GUI).
  • APARSER_PROXY_CHECKERS Default proxy checker groups, comma-separated.
  • APARSER_USE_PROXY Use proxies by default (true/false; default true).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect SEO Tools: A-Parser bridge yet

SEO Tools: A-Parser bridge runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect SEO Tools: A-Parser bridge

  • You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Marketing & social media that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SEO Tools: A-Parser bridge for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user seo-tools-aparser --env APARSER_PASSWORD=your-value -- npx -y seo-tools-mcp-aparser 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For APARSER_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SEO Tools: A-Parser bridge tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SEO Tools: A-Parser bridge key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SEO Tools: A-Parser bridge site ↗

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user seo-tools-aparser --env APARSER_PASSWORD=your-value -- npx -y seo-tools-mcp-aparser

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see SEO Tools: A-Parser bridge listed as connected

  6. Try it

    Use SEO Tools: A-Parser bridge and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using SEO Tools: A-Parser bridge or shows a SEO Tools: A-Parser bridge tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • APARSER_URL A-Parser API endpoint, e.g. http://IP:9091/API (Settings -> API).
  • APARSER_GOOGLE_PRESET Default config preset for SE::Google (preset name from the GUI).
  • APARSER_YANDEX_PRESET Default config preset for SE::Yandex (preset name from the GUI).
  • APARSER_PROXY_CHECKERS Default proxy checker groups, comma-separated.
  • APARSER_USE_PROXY Use proxies by default (true/false; default true).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SEO Tools: A-Parser bridge for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "seo-tools-aparser": { "command": "npx", "args": [ "-y", "seo-tools-mcp-aparser" ], "env": { "APARSER_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For APARSER_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SEO Tools: A-Parser bridge tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SEO Tools: A-Parser bridge key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SEO Tools: A-Parser bridge site ↗

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the SEO Tools: A-Parser bridge settings, APARSER_PASSWORD is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use SEO Tools: A-Parser bridge and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using SEO Tools: A-Parser bridge or shows a SEO Tools: A-Parser bridge tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • APARSER_URL A-Parser API endpoint, e.g. http://IP:9091/API (Settings -> API).
  • APARSER_GOOGLE_PRESET Default config preset for SE::Google (preset name from the GUI).
  • APARSER_YANDEX_PRESET Default config preset for SE::Yandex (preset name from the GUI).
  • APARSER_PROXY_CHECKERS Default proxy checker groups, comma-separated.
  • APARSER_USE_PROXY Use proxies by default (true/false; default true).

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a SEO Tools: A-Parser bridge key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server SEO Tools: A-Parser bridge for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "seo-tools-aparser": { "type": "stdio", "command": "npx", "args": [ "-y", "seo-tools-mcp-aparser" ], "env": { "APARSER_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For APARSER_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the SEO Tools: A-Parser bridge tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a SEO Tools: A-Parser bridge key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the SEO Tools: A-Parser bridge site ↗

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the SEO Tools: A-Parser bridge settings, APARSER_PASSWORD is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use SEO Tools: A-Parser bridge and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using SEO Tools: A-Parser bridge or shows a SEO Tools: A-Parser bridge tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • APARSER_URL A-Parser API endpoint, e.g. http://IP:9091/API (Settings -> API).
  • APARSER_GOOGLE_PRESET Default config preset for SE::Google (preset name from the GUI).
  • APARSER_YANDEX_PRESET Default config preset for SE::Yandex (preset name from the GUI).
  • APARSER_PROXY_CHECKERS Default proxy checker groups, comma-separated.
  • APARSER_USE_PROXY Use proxies by default (true/false; default true).

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use SEO Tools: A-Parser bridge💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user seo-tools-aparser --env APARSER_PASSWORD=your-value -- npx -y seo-tools-mcp-aparser

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "seo-tools-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "seo-tools-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "seo-tools-aparser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "your-value"
      }
    }
  }
}

Values you fill in

  • APARSER_URL env
    A-Parser API endpoint, e.g. http://IP:9091/API (Settings -> API).
  • APARSER_PASSWORD secret required env
    A-Parser API password (Settings -> API).
  • APARSER_GOOGLE_PRESET env
    Default config preset for SE::Google (preset name from the GUI).
  • APARSER_YANDEX_PRESET env
    Default config preset for SE::Yandex (preset name from the GUI).
  • APARSER_PROXY_CHECKERS env
    Default proxy checker groups, comma-separated.
  • APARSER_USE_PROXY env
    Use proxies by default (true/false; default true).

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
8 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings
Downloads per weeki
54/wk
Connection
Runs on your computer
Latest versioni
1.8.0
Published to registryi
Aug 25, 2026
Code last changedi
Oct 24, 2026
Maker
antohins
Packages
npm: seo-tools-mcp-aparser
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account antohins, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 25 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for seo-tools-mcp-aparser@1.8.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/antohins-seo-tools-mcp-aparser.svg)](https://mcp.popnx.com/en/servers/antohins-seo-tools-mcp-aparser)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 4124 servers in this category
  • Published to the registry more recently than 22% of the other 4124 servers in this category
  • Basic checks equal to or better than 99% of the other 4124 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SEO Tools: A-Parser bridge safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: APARSER_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 25 days ago, and the latest version (1.8.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

by ChatbotXIOGrowing★ 1.1K Stars for the whole repoUpdated 12 days ago

Runs in the cloud✓ service owner · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

by betterlyticsGrowing★ 196Updated 4 months ago

Runs in the cloud✓ service owner · betterlytics.io
Compared with similar ones
This one
SEO Tools: A-Parser bridge
RelaticleChatbotXX (Twitter) MCP Server by XquikBetterlyticsBibiGPT YouTube Video Summarizer
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoYesNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/44/44/4
LicenseMITAGPL-3.0NOASSERTIONMITAGPL-3.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

seo-tools-mcp

Русский | English

Восемь универсальных stdio MCP-серверов для SEO: доступ к SERP, Wordstat, Google Search Console, Google Analytics 4, Яндекс.Вебмастеру, Яндекс.Метрике и self-hosted A-Parser прямо из Claude Code (и любого MCP-клиента). Все инструменты read-only — ничего не публикуют и не меняют в твоих аккаунтах, вывод — строгий JSON. Машиночитаемо это заявлено аннотацией readOnlyHint; её намеренно нет у двадцати инструментов, каждый вызов которых тратит платный ресурс (запрос к XMLStock/XMLRiver, прокси-трафик A-Parser) — иначе клиент счёл бы их безобидными и перестал спрашивать подтверждение перед прогоном по большому пулу. К конкретному сайту не привязаны: дефолты (свойство GSC, свойство GA4, хост Вебмастера, счётчик Метрики) настраиваются на лету.

🛰 Эти серверы мы используем в продакшене в [PBN Workers](https://pbn-workers.com/ru/tools/seo-tools-mcp/) — инфраструктура поискового топа: семантика, PBN и сателлиты, автоматизация SEO. Нужен стабильный органический трафик — приходите.

СерверРабочие инструментыАвторизация
xmlstockxmlstock_serp, xmlstock_images, xmlstock_news, xmlstock_video, xmlstock_wordstat, xmlstock_wordstat_dynamics, xmlstock_wordstat_regions, xmlstock_wordstat_regions_tree, xmlstock_balanceAPI-ключ
xmlriverxmlriver_serp, xmlriver_images, xmlriver_news, xmlriver_maps, xmlriver_check_index, xmlriver_suggest, xmlriver_related_questions, xmlriver_balanceAPI-ключ
wordstatwordstat_frequency, wordstat_dynamics, wordstat_regions, wordstat_regions_treeApi-Key Yandex Cloud
gscgsc_query, gsc_inspect_url, gsc_list_sites, gsc_get_site, gsc_list_sitemaps, gsc_get_sitemapOAuth (все свойства аккаунта) / service account
ga4ga4_list_properties, ga4_property_details, ga4_metadata, ga4_check_compatibility, ga4_report, ga4_bytime, ga4_traffic_sources, ga4_geo, ga4_devices, ga4_top_pages, ga4_events, ga4_funnel, ga4_annotations, ga4_realtimeOAuth (все свойства аккаунта) / service account
ywmywm_hosts, ywm_summary, ywm_search_queries, ywm_queries_history, ywm_recommended_queries, ywm_popular, ywm_indexing_history, ywm_sqi_history, ywm_external_links, ywm_broken_links, ywm_diagnostics, ywm_important_urls, ywm_sitemapsOAuth (авто-refresh)
metrikametrika_report, metrika_bytime, metrika_counters, metrika_goals, metrika_traffic_sources, metrika_geo, metrika_devices, metrika_landing_behavior, metrika_search_phrases, metrika_top_landingsOAuth (авто-refresh)
aparseraparser_ping, aparser_status, aparser_proxies, aparser_parsers, aparser_parser_fields, aparser_get_preset, aparser_serp_google, aparser_serp_yandex, aparser_suggest, aparser_request, aparser_bulk_requestself-hosted A-Parser (URL + пароль API)

Где опубликовано: npm (восемь пакетов), официальный MCP Registry, [GitHub MCP Registry](https://github.com/mcp/antohins/seo-tools-mcp-gsc) (все восемь серверов), маркетплейс плагинов Claude Code (см. ниже) и .mcpb-бандлы в релизах.

У каждого сервера дополнительно есть auth-инструменты _auth_status и _set_credentials (см. Интерактивная авторизация).

Инструменты по сервисам

xmlstock — SERP Google/Яндекс
  • xmlstock_serp — веб-выдача Google/Яндекса (органика + подсветки + SERP-фичи): регион, устройство, safe search, сортировка (Яндекс), период, рекламные блоки; третий движок yandex_xml — официальный Яндекс XML (groupby до 100 за 1 запрос, hlword на любых устройствах, статистика found/found-docs; тариф от 24 ₽/1000)
  • xmlstock_images — поиск картинок Google (url страницы + url изображения + заголовок)
  • xmlstock_news — новости Google (заголовок, источник, дата, сниппет)
  • xmlstock_video — видео Google (url, заголовок, превью, хост, канал, длительность)
  • xmlstock_wordstat — Яндекс Wordstat: топ + похожие запросы с частотностью (можно по региону), операторы Wordstat
  • xmlstock_wordstat_dynamics — динамика частотности по времени (день/неделя/месяц)
  • xmlstock_wordstat_regions — спрос по регионам (count, share, affinity index + имена регионов)
  • xmlstock_wordstat_regions_tree — дерево регионов Wordstat (id + имя + путь)
  • xmlstock_balance — баланс аккаунта / проверка ключа (бесплатно)

Wordstat через XMLStock — тем же ключом XMLSTOCK_*, что и SERP; не нужен Yandex Cloud (в отличие от отдельного сервера wordstat).

xmlriver — SERP Google/Яндекс + проверка индексации
  • xmlriver_serp — органика Google/Яндекса (глубина добирается пагинацией: каждые 10 позиций = 1 платный запрос), флаг наличия AI Overview; опция includeAIOverview — полный текст Обзора от ИИ + цитируемые ссылки (платный ai=1, только Google); includeAdditional — доп. SERP-блоки Google из (knowledge_graph, localresultsplace, rs и др.; наполнение зависит от платных опций кабинета XMLRiver, непришедшие блоки — в additional.unavailable); гео-таргетинг Google — location (город → loc, «Moscow»/«1011969») и country (ISO/числовой id, автовыводится из города); device — desktop/mobile/tablet, os (ios/android) отправляется только при device=mobile
  • xmlriver_images — картинки Google (страница + url картинки + заголовок + источник + размеры); гео — location/country
  • xmlriver_news — новости Google (заголовок, источник, дата, сниппет), фильтр по времени; гео — location/country
  • xmlriver_maps — поиск заведений по Google Maps (setab=maps, обязательные zoom 1–15 и coords «широта,долгота», count 5–50): название, рейтинг, адрес, телефон, сервисы, координаты, place_id, число отзывов. ВАЖНО: формат по доке, лайвом не подтверждён (на тестовом аккаунте эндпоинт устойчиво отвечает кодом 500 — вероятно, нужна платная опция кабинета)
  • xmlriver_check_index — проверка индексации URL в Google/Яндексе (inindex)
  • xmlriver_suggest — поисковые подсказки Google (до 50 фраз за вызов, платно за каждую фразу); гео подсказок — location/country
  • xmlriver_related_questions — блок «Вопросы по теме» / People Also Ask Google (вопросы всегда; ответы — только при включённой платной опции «Related Questions с ответами» в кабинете)
  • xmlriver_balance — баланс аккаунта / проверка ключа (бесплатно)
wordstat — частотности Яндекса
  • wordstat_frequency — широкая и точная частотность, уточняющие запросы (related) и ассоциации
  • wordstat_dynamics — частотность по времени (день/неделя/месяц)
  • wordstat_regions — распределение по регионам с индексом аффинити и именами регионов
  • wordstat_regions_tree — полное дерево регионов Вордстата (id + имя)
gsc — Google Search Console
  • gsc_query — Search Analytics (клики/показы/CTR/позиция), авто-пагинация, dataState final/all, произвольные фильтры измерений (filters, AND-семантика) и aggregationType (auto/byProperty/byPage)
  • gsc_inspect_url — URL Inspection: статус индексации, покрытие, canonical, последний обход, mobile usability, rich results
  • gsc_list_sites — свойства, доступные авторизации
  • gsc_get_site — уровень доступа к свойству
  • gsc_list_sitemaps — отправленные sitemap со статусом
  • gsc_get_sitemap — детали одного sitemap

Даты Search Analytics — по Pacific Time (не МСК); история ~16 месяцев; финальные данные отстают на ~2-3 дня (свежие — dataState=all); ctr в ответе — доля 0..1.

ga4 — Google Analytics 4
  • ga4_list_properties — свойства GA4, доступные авторизации (отсюда берётся propertyId — это не Measurement ID G-XXXXXXX)
  • ga4_metadata — какие измерения и метрики доступны в ЭТОМ свойстве, включая кастомные (customEvent:…); поиск подстрокой, blockedReasons (по такой метрике отчёт вернёт нули) и type (целое/дробное для metricFilters)
  • ga4_check_compatibility — совместима ли связка измерений/метрик в этом свойстве, без тяжёлого отчёта; при несовместимости — какие поля убрать
  • ga4_report — произвольный отчёт: любые измерения × метрики, фильтры по измерениям, сортировка (полный Data API runReport)
  • ga4_bytime — динамика метрик по времени (день/час/неделя/месяц)
  • ga4_traffic_sources — источники трафика: группа каналов, source/medium, кампания; organicOnly — только органика
  • ga4_geo — страна/регион/город
  • ga4_devices — тип устройства/ОС/браузер
  • ga4_top_pages — топ страниц по pagePath, странице входа или заголовку; фильтры organicOnly и pathContains
  • ga4_events — события по eventName; keyEventsOnly — только ключевые события (бывшие конверсии)
  • ga4_realtime — отчёт в реальном времени (последние 30 минут)
  • ga4_funnel — воронка (runFunnelReport): сколько дошло до каждого шага и где отвалились; шаг = событие и/или условия по измерениям, разбивка по измерению. Внутри шагов действует схема Exploration API (pagePath там недоступен), корзина квоты отдельная и запрос дороже обычного отчёта
  • ga4_annotations — аннотации свойства: пометки на датах, включая созданные самой GA4 (systemGenerated) — частое объяснение необъяснимого скачка в динамике
  • ga4_property_details — карточка свойства: таймзона отчётов, валюта, уровень сервиса (STANDARD/360) и потоки данных с их Measurement ID G-XXXXXXX

Во всех отчётных инструментах есть includeQuota — сколько «токенов» Data API съел запрос и сколько осталось на час/сутки.

Единицы и даты: bounceRate/engagementRate GA4 отдаёт долей 0..1 (не процентами); даты считаются в таймзоне свойства — принимаются YYYY-MM-DD и ключевые слова GA4 (today, yesterday, 28daysAgo), фактическая таймзона возвращается в ответе. В ответах есть totalRows/truncated, а thresholded: true означает, что часть данных скрыта порогом конфиденциальности GA4.

ywm — Яндекс.Вебмастер
  • ywm_hosts — id пользователя + подтверждённые сайты
  • ywm_summary — ИКС, страниц в поиске, исключено, проблемы сайта по важности
  • ywm_search_queries — аналитика запросов по URL (~2 недели по умолчанию; переопределяется dateFrom/dateTo)
  • ywm_queries_history — суммарные показы/клики/позиции по времени
  • ywm_recommended_queries — приближённые рекомендованные запросы (спрос + недобор кликов)
  • ywm_popular — популярные запросы хоста
  • ywm_indexing_history — страниц в поиске по времени
  • ywm_sqi_history — ИКС по времени
  • ywm_external_links — выборка внешних ссылок + общее число
  • ywm_broken_links — битые внутренние/внешние ссылки
  • ywm_diagnostics — проблемы сайта
  • ywm_important_urls — отслеживаемые URL со статусом индексации/поиска
  • ywm_sitemaps — sitemap со статусом
metrika — Яндекс.Метрика
  • metrika_report — произвольный отчёт: любые dimensions × metrics, фильтры, сортировка (полный Stat API)
  • metrika_bytime — метрики по времени (день/неделя/месяц/час)
  • metrika_traffic_sources — визиты/пользователи/отказы по источникам трафика
  • metrika_geo — визиты по стране/региону/городу
  • metrika_devices — визиты по устройству/ОС/браузеру
  • metrika_goals — список целей (конверсий)
  • metrika_counters — доступные счётчики
  • metrika_landing_behavior — поведение на посадочных + достижения целей
  • metrika_search_phrases — поисковые фразы (органика)
  • metrika_top_landings — т

Only the beginning is shown; read the rest in the repo