Marketing MCP server · seo-audit-tool

Audit the HTML your pages actually return.

Give your MCP client a public page, plain-text draft, sitemap, or pair of URLs. SEO Audit Tool fetches and parses the source directly, then returns a structured Markdown report with rule-based findings and recommendations.

5 shipped MCP tools 3 calls total free No external API keys Node.js 18+
Run with npx Plans & pricing 
npx -y seo-audit-tool

What it does

Five focused tools, exposed through MCP

Each tool accepts only the input shown below. Reports are generated from the supplied text or the HTML/XML returned by the supplied URL.

audit_page

Audits one URL for title and meta description length, heading hierarchy, image alt coverage, link counts, response size, viewport metadata, structured data, canonical markup, and Open Graph tags.

Input: url

Returns: a 0–100 score, A–F grade, issues by severity, and recommendations.

analyze_keywords

Analyzes supplied plain text for one-, two-, and three-word phrases, counts, density percentages, and a single-document TF-IDF approximation.

Input: text

Returns: keyword tables, suggested focus phrases, related suggestions, and tips.

check_links

Extracts up to 100 unique links from one page and checks them with 10 concurrent requests, using HEAD with a GET fallback where needed.

Input: url

Returns: broken and redirected links, internal/external classification, and rel attributes.

analyze_sitemap

Parses an XML sitemap, detects sitemap indexes, checks duplicates and the 50,000-URL limit, validates lastmod values, and groups URL paths.

Input: url

Returns: validation status, statistics, issues, URL patterns, and sample entries.

compare_pages

Fetches two pages in parallel and compares their rule-based SEO scores, metadata lengths, headings, word counts, images, links, response sizes, viewport tags, and structured data.

Inputs: url_a, url_b

Returns: a side-by-side table, winner, and recommendations for the lower-scoring page.

Agent workflows

Three calls an agent can make

These are representative MCP arguments using the exact shipped tool schemas.

01 · Pre-publish page review

Find on-page issues before launch

When asked to review a public page, the agent calls audit_page and turns the scored findings into a prioritized editing checklist.

Tool: audit_page

{
  "url": "https://example.com"
}
02 · Draft keyword review

Inspect the language in a draft

The agent passes plain text to analyze_keywords to surface repeated phrases, density, focus-keyword suggestions, and related phrase suggestions before publication.

Tool: analyze_keywords

{
  "text": "Technical SEO audits help teams find missing metadata, heading issues, and image alt text before publishing."
}
03 · Side-by-side review

Compare two public pages

For a relative review, the agent calls compare_pages and uses its rule-based metric table and winner to identify where the lower-scoring page differs.

Tool: compare_pages

{
  "url_a": "https://example.com",
  "url_b": "https://example.org"
}

Quickstart

Run locally through npm

The package supports stdio by default. No install step or external API key is required.

Open your client's config file

  • Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json

    Windows: %APPDATA%\Claude\claude_desktop_config.json. In the app: Settings → Developer → Edit Config.

  • Cursor ~/.cursor/mcp.json

    Or .cursor/mcp.json inside a single project.

  • Windsurf ~/.codeium/windsurf/mcp_config.json

    Cascade panel → MCP icon → edit the raw config.

Paste this entry

All three clients accept the same object. If the file already has an mcpServers block, add just the "seo-audit-tool" entry inside it.

mcpServers entry
{
  "mcpServers": {
    "seo-audit-tool": {
      "command": "npx",
      "args": ["-y", "seo-audit-tool"]
    }
  }
}

No env block is needed to start: the first 3 tool calls total across this server's tools run without a license.

Using Claude Code instead? One command, no file

shell
$ claude mcp add --transport stdio seo-audit-tool -- npx -y seo-audit-tool

Check it registered with claude mcp list. Add a key later with --env LICENSE_KEY=your-key placed before --transport.

Restart the client, then confirm it loaded

  • Claude Desktop: quit and reopen the app, then look for SEO Audit Tool in the tools/plugin menu.
  • Cursor: Settings → Customize → MCP; the server should list its tools.
  • Windsurf: reload Cascade; the server appears under the MCP panel.
  • Claude Code: run claude mcp list and look for ✔ Connected.

Running npx -y seo-audit-tool in a terminal looks frozen — that is correct. It is a stdio server: it waits silently for an MCP client on stdin and never returns a prompt. Press Ctrl+C to exit. Use the config above rather than the bare command; your client starts the process for you.

Add your license key when you buy

A key arrives on screen right after checkout. Add it as an environment variable in the same entry:

mcpServers entry with license
{
  "mcpServers": {
    "seo-audit-tool": {
      "command": "npx",
      "args": ["-y", "seo-audit-tool"],
      "env": {
        "LICENSE_KEY": "paste-your-key-here"
      }
    }
  }
}

Keys are verified offline against a public key compiled into the package — no account, no network check, no usage reporting. Lost the key? Recover it here. More detail on the FAQ.

Scope

Direct source analysis, with clear boundaries

In scope

  • Public HTTP or HTTPS pages and sitemap URLs reachable from the local process.
  • HTML metadata, headings, images, links, viewport markup, structured data, canonical tags, and Open Graph tags.
  • Plain-text n-grams, density, and single-document TF-IDF approximation.
  • Up to 100 unique links per page, with a 15-second timeout per request.
  • Individual XML sitemaps and sitemap-index detection.

It does not

  • Render JavaScript or inspect a browser's post-rendered DOM.
  • Measure Core Web Vitals or real browser load time; page size is the fetched response size.
  • Provide search rankings, search volume, backlink data, analytics, or webmaster-console data.
  • Edit a page, apply fixes, submit a sitemap, or crawl an entire site.
  • Recursively audit child sitemaps from an index; call analyze_sitemap for each child URL.

Start with the shipped tools

Three real calls, then choose a plan.

Run the package through npx, connect it to your MCP client, and use the same five tools available to licensed plans during the three-call trial.

Copy the config Compare Basic and Pro