Who maintains SEO Tools: A-Parser bridge?

SEO Tools: A-Parser bridge is maintained by antohins, which publishes 9 MCP servers (47 total versions) tracked on MCP Toplist.

Is SEO Tools: A-Parser bridge listed on the Official MCP Registry?

Yes — SEO Tools: A-Parser bridge is listed on the Official MCP Registry.

How many versions does SEO Tools: A-Parser bridge have?

MCP Toplist tracks 4 versions of SEO Tools: A-Parser bridge, most recently published on Aug 25, 2026.

Where can I find the source code for SEO Tools: A-Parser bridge?

The source code for SEO Tools: A-Parser bridge is hosted at github.com/antohins/seo-tools-mcp.

SERVER

SEO Tools: A-Parser bridge

Rank #22,073

io.github.antohins/seo-tools-mcp-aparser

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

4 versions

3 GitHub stars

by antohins (9 servers)View repository ↗

First listed

Jul 17, 2026

Last publish date

Aug 25, 2026

OVERVIEW

SEO Tools: A-Parser bridge is a Model Context Protocol (MCP) server published by antohins. It ranks #22,073 of 115,591 servers tracked on MCP Toplist, and its repository has 3 GitHub stars. SEO Tools: A-Parser bridge is listed on Official MCP, with 4 tracked versions. It was first listed on Jul 17, 2026 and most recently updated on Aug 25, 2026.

STANDING

#22,073of 115,591 tracked serversTop 25%

Ranks ahead of 93,518 of 115,591 servers on MCP Toplist.

CONNECT

Use SEO Tools: A-Parser bridge

No setupRuns out of the box

No credentials or required configuration declared — add it to your MCP client and go.

npm package

claude mcp add seo-tools-mcp-aparser -e "APARSER_URL=<your APARSER_URL>" -e "APARSER_PASSWORD=<your APARSER_PASSWORD>" -e "APARSER_GOOGLE_PRESET=<your APARSER_GOOGLE_PRESET>" -e "APARSER_YANDEX_PRESET=<your APARSER_YANDEX_PRESET>" -e "APARSER_PROXY_CHECKERS=<your APARSER_PROXY_CHECKERS>" -e "APARSER_USE_PROXY=<your APARSER_USE_PROXY>" -- npx -y seo-tools-mcp-aparser

Replace each placeholder with your own value before saving.

npm package

[mcp_servers.seo-tools-mcp-aparser]
command = "npx"
args = ["-y", "seo-tools-mcp-aparser"]

[mcp_servers.seo-tools-mcp-aparser.env]
APARSER_URL = "<your APARSER_URL>"
APARSER_PASSWORD = "<your APARSER_PASSWORD>"
APARSER_GOOGLE_PRESET = "<your APARSER_GOOGLE_PRESET>"
APARSER_YANDEX_PRESET = "<your APARSER_YANDEX_PRESET>"
APARSER_PROXY_CHECKERS = "<your APARSER_PROXY_CHECKERS>"
APARSER_USE_PROXY = "<your APARSER_USE_PROXY>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

npm package

{
  "mcpServers": {
    "seo-tools-mcp-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_URL": "<your APARSER_URL>",
        "APARSER_PASSWORD": "<your APARSER_PASSWORD>",
        "APARSER_GOOGLE_PRESET": "<your APARSER_GOOGLE_PRESET>",
        "APARSER_YANDEX_PRESET": "<your APARSER_YANDEX_PRESET>",
        "APARSER_PROXY_CHECKERS": "<your APARSER_PROXY_CHECKERS>",
        "APARSER_USE_PROXY": "<your APARSER_USE_PROXY>"
      }
    }
  }
}

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

npm package

{
  "mcpServers": {
    "seo-tools-mcp-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_URL": "<your APARSER_URL>",
        "APARSER_PASSWORD": "<your APARSER_PASSWORD>",
        "APARSER_GOOGLE_PRESET": "<your APARSER_GOOGLE_PRESET>",
        "APARSER_YANDEX_PRESET": "<your APARSER_YANDEX_PRESET>",
        "APARSER_PROXY_CHECKERS": "<your APARSER_PROXY_CHECKERS>",
        "APARSER_USE_PROXY": "<your APARSER_USE_PROXY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

npm package

{
  "servers": {
    "seo-tools-mcp-aparser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_URL": "<your APARSER_URL>",
        "APARSER_PASSWORD": "<your APARSER_PASSWORD>",
        "APARSER_GOOGLE_PRESET": "<your APARSER_GOOGLE_PRESET>",
        "APARSER_YANDEX_PRESET": "<your APARSER_YANDEX_PRESET>",
        "APARSER_PROXY_CHECKERS": "<your APARSER_PROXY_CHECKERS>",
        "APARSER_USE_PROXY": "<your APARSER_USE_PROXY>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

npm package

{
  "mcpServers": {
    "seo-tools-mcp-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_URL": "<your APARSER_URL>",
        "APARSER_PASSWORD": "<your APARSER_PASSWORD>",
        "APARSER_GOOGLE_PRESET": "<your APARSER_GOOGLE_PRESET>",
        "APARSER_YANDEX_PRESET": "<your APARSER_YANDEX_PRESET>",
        "APARSER_PROXY_CHECKERS": "<your APARSER_PROXY_CHECKERS>",
        "APARSER_USE_PROXY": "<your APARSER_USE_PROXY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

npm package

{
  "mcpServers": {
    "seo-tools-mcp-aparser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_URL": "<your APARSER_URL>",
        "APARSER_PASSWORD": "<your APARSER_PASSWORD>",
        "APARSER_GOOGLE_PRESET": "<your APARSER_GOOGLE_PRESET>",
        "APARSER_YANDEX_PRESET": "<your APARSER_YANDEX_PRESET>",
        "APARSER_PROXY_CHECKERS": "<your APARSER_PROXY_CHECKERS>",
        "APARSER_USE_PROXY": "<your APARSER_USE_PROXY>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.antohins%2Fseo-tools-mcp-aparser.svg)](https://mcptoplist.com/server/io.github.antohins%2Fseo-tools-mcp-aparser)

HTML

<a href="https://mcptoplist.com/server/io.github.antohins%2Fseo-tools-mcp-aparser"><img src="https://mcptoplist.com/badge/io.github.antohins%2Fseo-tools-mcp-aparser.svg" alt="MCP Toplist: Top 25% of 115,591" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

REGISTRIES

Listed on 1 registry

Official MCP

ORGANIZATION

antohins

Organization

antohins

Servers in org

Versions across org

VERSIONS

Available versions (4)

Version	Published
1.8.0	Aug 25, 2026
1.7.0	Aug 8, 2026
1.5.1	Aug 7, 2026
1.4.0	Aug 4, 2026

FAQ

Frequently asked questions

Who maintains SEO Tools: A-Parser bridge?: SEO Tools: A-Parser bridge is maintained by antohins, which publishes 9 MCP servers (47 total versions) tracked on MCP Toplist.
Is SEO Tools: A-Parser bridge listed on the Official MCP Registry?: Yes — SEO Tools: A-Parser bridge is listed on the Official MCP Registry.
How many versions does SEO Tools: A-Parser bridge have?: MCP Toplist tracks 4 versions of SEO Tools: A-Parser bridge, most recently published on Aug 25, 2026.
Where can I find the source code for SEO Tools: A-Parser bridge?: The source code for SEO Tools: A-Parser bridge is hosted at github.com/antohins/seo-tools-mcp.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers