RankCLI logo

RankCLI

Runs local SEO and GEO audits on supplied webpage HTML and robots.txt, with checks for AI crawlers, performance, schema, security, and mobile SEO.

Install RankCLI

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "rankcli-2": {
      "command": "npx",
      "args": [
        "-y",
        "@rankcli/mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

RankCLI provides local SEO and GEO analysis tools for AI assistants through MCP. It examines webpage HTML or robots.txt supplied by the MCP host, covering AI crawler access, citation readiness, Core Web Vitals estimates, structured data, security headers, images, internal links, and mobile SEO. Reach for it when auditing a site before deployment or investigating visibility in ChatGPT, Claude, Perplexity, or Gemini. An optional account connection enables RankCLI dashboard history, scheduled monitoring, and GitHub auto-fix pull requests without changing the local analysis tools.

Use cases

  • Audit a webpage before deployment
  • Check whether AI crawlers can access a site
  • Validate JSON-LD and generate schema templates
  • Review performance, security, image, and mobile SEO issues
  • Inspect internal linking and orphan-page risk

Key features

  • Local SEO and GEO analysis from supplied HTML
  • AI crawler and robots.txt inspection
  • Estimated Core Web Vitals checks
  • Schema.org validation and JSON-LD generation
  • Security header, image, link, and mobile audits
  • Optional RankCLI account connection

Tools15

What RankCLI lets your agent do. Expand a tool for its parameters.

Verified live~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 45d

What it can do

From the 15 tools this server returned when we ran it.

Can delete or modify data · 1Handles credentials · 1Read-only tools · 14
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age254 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @rankcli/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.3kPackage downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Tools exposed15Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How RankCLI works

What RankCLI MCP server does

RankCLI exposes a collection of SEO and GEO checks to MCP-compatible AI assistants. Its primary input is webpage HTML that the assistant or host already has, along with robots.txt content where relevant. The local tools do not require a signup or API key, and their analysis runs inside the MCP host rather than sending audit data to RankCLI servers.

The central seo_analyze tool combines checks for AI-search optimization, estimated Core Web Vitals, Schema.org structured data, security headers, mobile readiness, image handling, and internal linking. Individual tools are available when a narrower diagnostic or generated configuration is more useful than a complete audit.

How it works

An MCP host starts the package as a local process and makes its tools available to an AI assistant. The host can fetch a page and pass its HTML to the tools, or an agent can work with HTML already present in a project or build output. The server analyzes that material locally.

GEO checks examine whether AI crawlers can access a site, how robots.txt rules affect bots such as GPTBot, ClaudeBot, and PerplexityBot, whether JavaScript is needed to reveal content, and whether the page contains signals useful for extraction and citation. Other checks estimate performance from HTML, inspect JSON-LD, review security-related headers, and assess images, links, and mobile layout signals.

rankcli_connect is the exception to the local-only workflow. It opens a browser approval flow for a RankCLI account at rankcli.dev, or reuses an existing session. rankcli_disconnect removes this local connection without deleting the account or revoking other API keys.

Setup and configuration

Install the server with npx:

config.json
{
  "mcpServers": {
    "rankcli": {
      "command": "npx",
      "args": ["-y", "@rankcli/mcp-server"]
    }
  }
}

Claude Code can add the same server with claude mcp add rankcli -- npx -y @rankcli/mcp-server. Claude Desktop also supports installing the latest .mcpb release, while Cursor and VS Code provide install links. The package can be used from Claude Desktop, Claude Code, Cursor, VS Code, Codex, and Windsurf.

The local server does not need an environment variable, API key, or RankCLI account for its analysis tools. Account linking is optional and is used for dashboard history, scheduled monitoring, and GitHub auto-fix pull requests.

Tools and capabilities

  • seo_analyze runs the combined audit.
  • seo_geo_check reviews AI-search visibility, crawler access, content structure, and citation readiness.
  • seo_robots_ai reports which known AI crawlers are allowed or blocked.
  • seo_generate_robots creates a robots.txt intended to permit major AI crawlers.
  • seo_core_web_vitals estimates LCP, CLS, INP, and TTFB and flags common HTML-related performance issues.
  • seo_structured_data validates JSON-LD and common Schema.org types; seo_generate_schema creates templates for article, product, FAQ, local-business, and website pages.
  • seo_security_headers grades HTTPS, HSTS, CSP, X-Frame-Options, and related protections; seo_generate_security_headers produces recommended configuration.
  • seo_images, seo_internal_links, and seo_mobile inspect image metadata and loading, link structure, viewport and touch-target signals, font sizing, content width, and PWA readiness.
  • seo_ai_crawlers provides user-agent and purpose information for known AI crawlers.
  • rankcli_connect and rankcli_disconnect manage the optional local account connection.

Limitations and notes

The local tools work from HTML and robots.txt supplied by the user or MCP host. They do not provide a remote crawl of a URL by themselves. Core Web Vitals are estimates based on HTML analysis rather than field measurements. Account-linked features require the separate connection flow, while the audit tools remain usable without it.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RankCLI

RankCLI is an MCP server that connects AI assistants to local webpage HTML and robots.txt inputs, with tools for SEO audits, GEO visibility, crawler permissions, Core Web Vitals, structured data, security headers, images, internal links, and mobile checks. It also supports optional account linking for RankCLI features.

Install RankCLI with the standard MCP configuration using `npx -y @rankcli/mcp-server`. Claude Code also supports `claude mcp add rankcli -- npx -y @rankcli/mcp-server`; Claude Desktop can use the latest `.mcpb` release, and Cursor and VS Code provide install links.

No, the local analysis tools require neither an API key nor an account. They run in the MCP host against HTML or robots.txt supplied by the user or host. Account linking is optional for dashboard history, scheduled monitoring, and GitHub auto-fix pull requests.

RankCLI is documented for Claude Desktop, Claude Code, Cursor, VS Code, Codex, and Windsurf. It runs as a standard local `npx` MCP process, with client-specific installation options for several of those applications.

The local server analyzes HTML and robots.txt supplied by the user or MCP host rather than performing a remote URL crawl itself. An MCP host can fetch a page and pass its HTML to RankCLI for analysis.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRankCLI AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rankcli-2?style=directory)](https://allmcps.com/mcp/rankcli-2)
HTML Embed
<a href="https://allmcps.com/mcp/rankcli-2"><img src="https://allmcps.com/api/badge/rankcli-2?style=directory" alt="RankCLI on AllMCPs" /></a>