We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

SEO Tools: A-Parser

MCP server by antohins

Run Google and Yandex SERP, search suggestions and other A-Parser parsers through a self-hosted A-Parser API, read-only.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install SEO Tools: A-Parser

Runs on your machine. Your client starts it with this command:

npx -y seo-tools-mcp-aparser

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

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

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/seo-tools-a-parser

About

Connects to your own A-Parser instance through its API. You can check the instance status and proxies, list parsers and their fields, read presets, fetch Google and Yandex search results, collect search suggestions, and run any of the 150+ parsers with single or bulk requests.

Runs locally over stdio with npx (package seo-tools-mcp-aparser). It needs the A-Parser API URL and API password, set as environment variables. Optional variables set default Google and Yandex presets, proxy checker groups and proxy use. Part of the seo-tools-mcp collection, which also covers other SEO services.

What you can do

  • Check A-Parser connectivity and task status
  • List proxies, parsers and parser fields
  • Read saved config presets
  • Fetch Google SERP results
  • Fetch Yandex SERP results
  • Collect search suggestions
  • Run any parser with single or bulk requests

Tools

SEO Tools: A-Parser lists its tools only to clients with a key, so we can’t show them here.

Example prompts

  • Ping my A-Parser and show its current status

  • Get the Google SERP for 'buy running shoes' using A-Parser

  • Collect search suggestions for 'seo audit' with A-Parser

  • List the parsers available in my A-Parser and their fields

Set up

Every client starts SEO Tools: A-Parser on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio seo-tools-a-parser --env "APARSER_PASSWORD=<YOUR_APARSER_PASSWORD>" -- npx -y seo-tools-mcp-aparser
  1. Start Claude Code and type /mcp. seo-tools-a-parser should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "seo-tools-a-parser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "<YOUR_APARSER_PASSWORD>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "seo-tools-a-parser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "<YOUR_APARSER_PASSWORD>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "seo-tools-a-parser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "${input:aparser-password}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "aparser-password",
      "description": "APARSER_PASSWORD",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "seo-tools-a-parser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "<YOUR_APARSER_PASSWORD>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add seo-tools-a-parser --env "APARSER_PASSWORD=<YOUR_APARSER_PASSWORD>" -- npx -y seo-tools-mcp-aparser

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.seo-tools-a-parser]
command = "npx"
args = ["-y", "seo-tools-mcp-aparser"]
env = { APARSER_PASSWORD = "<YOUR_APARSER_PASSWORD>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "APARSER_PASSWORD=<YOUR_APARSER_PASSWORD>" seo-tools-a-parser npx -- -y seo-tools-mcp-aparser

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "seo-tools-a-parser": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-aparser"
      ],
      "env": {
        "APARSER_PASSWORD": "<YOUR_APARSER_PASSWORD>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

Embed

Show SEO Tools: A-Parser in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![SEO Tools: A-Parser on mcp.tc](https://mcp.tc/i/seo-tools-a-parser/badge.svg)](https://mcp.tc/i/seo-tools-a-parser)
HTML
<a href="https://mcp.tc/i/seo-tools-a-parser"><img src="https://mcp.tc/i/seo-tools-a-parser/badge.svg" alt="SEO Tools: A-Parser on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/seo-tools-a-parser.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/seo-tools-a-parser" title="SEO Tools: A-Parser on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/seo-tools-a-parser.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SEO Tools: A-Parser card to your site.

Markdown
Add the mcp.tc card for SEO Tools: A-Parser, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/seo-tools-a-parser.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="seo-tools-a-parser"><a href="https://mcp.tc/i/seo-tools-a-parser">SEO Tools: A-Parser on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![SEO Tools: A-Parser on mcp.tc](https://mcp.tc/i/seo-tools-a-parser/badge.svg)](https://mcp.tc/i/seo-tools-a-parser)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow SEO Tools: A-Parser and we’ll email you when something changes.

  1. , Automatic check

    Tracking started: version 1.8.0.

FAQ

Can I paste mcp.tc/i/seo-tools-a-parser into my MCP client?

No. SEO Tools: A-Parser runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y seo-tools-mcp-aparser.

Does SEO Tools: A-Parser need an API key?

Yes. It reads APARSER_PASSWORD from its environment, and APARSER_PASSWORD is a secret. Put the value in your client’s config on your own machine, never in a shared file.

Is SEO Tools: A-Parser a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y seo-tools-mcp-aparser, which needs Node.js.

What can SEO Tools: A-Parser do?

You can check A-Parser connectivity and task status, list proxies, parsers and parser fields and read saved config presets.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to SEO Tools: A-Parser?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read SEO Tools: A-Parser’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with antohins. This page was built from SEO Tools: A-Parser’s public metadata, last checked on 5 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.