mcpbeat Sign in

SEOcrawl AI MCP Server

answering

SEOcrawl AI is answering right now. Last checked 11 min ago.

Live Google Search Console data, keyword/page analysis, site audit and SEO tasks from SEOcrawl AI.

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
341 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

SEOcrawl AI does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.seocrawl.ai
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.seocrawl.ai"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.seocrawl.ai"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.seocrawl.ai"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.seocrawl.ai"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.seocrawl.ai streamable-http sign-in 158 ms 11 min ago

Alternatives to SEOcrawl AI

same job, measured the same way
That SEO Agent
by thatseoagent

SEO analysis for sites you own: Google Search Console, GA4, PageSpeed, and full site audits.

answering
CalmSEO
by calmseo

SEO MCP server for keyword research, SERP analysis, audits, and Search Console workflows.

answering
Google Search Console MCP
by mcpsearchconsole

Google Search Console SEO analytics, keyword rankings, URL inspection, sitemaps, PageSpeed checks.

answering
MCP Ads
by mcp-ads

Run Google Ads, Meta Ads, GA4 and Search Console from chat: read, audit and launch campaigns.

answering
Google Search Console
by akzar1el

Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.

26 installs/wk answering
Climbpast
by archievi

Read and edit GA4, Search Console and Google Tag Manager from any MCP client. 29 tools.

answering
Cituna MCP
by cituna

Track how 6 AI engines cite your brand, daily, with live Google Search Console.

71 installs/wk local only
Gtasks MCP
by alvinjchoi

Manage Google Tasks via MCP: list, search, create, update, move, and clear tasks.

119 installs/wk local only

SEOcrawl AI — questions

Answers built from our own checks of this server.

Why is there no tool list for SEOcrawl AI?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SEOcrawl AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 341 ms. The bar chart above shows every period we have measured.
How do I connect SEOcrawl AI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SEOcrawl AI?
No API key is involved. SEOcrawl AI answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SEOcrawl AI?
It answers our handshake in 341 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.