🔎 SEO & GEO MCP

Give Claude, ChatGPT, Cursor, VS Code, and other compatible AI clients live SEO research and generative-engine optimization capabilities through one hosted MCP endpoint.

SEO & GEO MCP combines search-result analysis, keyword intelligence, backlink research, technical audits, domain and content analysis, local-business research, e-commerce intelligence, and AI visibility workflows. It runs in Apify Standby mode, so your AI can discover and call the tools directly during a conversation.

You only need an Apify API token. The Actor owner manages the underlying data-service account, and usage is passed through as simple Apify Pay-per-Event billing. You do not need another API login, password, OAuth client ID, or OAuth client secret.

Quick Start: connect in under a minute

Get your personal token from Apify Integrations. Then copy this exact URL and replace the uppercase placeholder with your token:

https://mrbridge--seo-geo-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

If your token begins with apify_api_, replace the complete YOUR_APIFY_API_TOKEN text—not just the word TOKEN. Keep the URL on one line and keep https:// at the beginning.

Claude

In Claude, open Settings → Connectors, choose the option to add a custom connector, and paste the completed URL. If the advanced form displays OAuth Client ID and OAuth Client Secret, leave both fields empty: authentication is already handled by the Apify token in the URL.

After saving, ask Claude:

List the SEO & GEO tools available through this connector.

A cold start after inactivity typically takes 5–15 seconds while the Standby server starts, although platform load can occasionally add more time.

ChatGPT

If custom MCP connectors are enabled for your ChatGPT plan or workspace, open connector settings, add a remote MCP server, and paste the same completed URL. No separate OAuth application is required.

Cursor

Add the server in Cursor's MCP settings, or use this structure in .cursor/mcp.json:

{
  "mcpServers": {
    "seo-geo": {
      "url": "https://mrbridge--seo-geo-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN"
    }
  }
}

VS Code

Add a remote HTTP MCP server through the MCP settings, or use this structure in .vscode/mcp.json:

{
  "servers": {
    "seo-geo": {
      "type": "http",
      "url": "https://mrbridge--seo-geo-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN"
    }
  }
}

Claude Code and other MCP clients

Choose Streamable HTTP or remote HTTP as the transport and use the same /mcp?token=... URL. If a client supports custom authorization headers, you can instead connect to:

https://mrbridge--seo-geo-mcp.apify.actor/mcp

and send:

Authorization: Bearer YOUR_APIFY_API_TOKEN

Do not send the token both ways. Never share your completed connection URL, because it contains access to your Apify account.

What you can ask your AI

The complete catalog is always available; there is no module-selection setup.

Module	Typical work	Example prompt
SERP	Search-engine result pages and ranking features	“Show the current organic results for this query in France and summarize the competing page types.”
KEYWORD_DATA	Search demand, trends, CPC, and keyword metrics	“Compare demand and seasonality for these product keywords.”
SEO_LABS	Keyword ideas, rankings, competitors, and domain opportunities	“Find low-difficulty topics that three competitors rank for but my site does not.”
BACKLINKS	Links, referring domains, anchors, and authority signals	“Audit this domain's backlink profile and flag risky anchor concentration.”
ON_PAGE	Technical crawling and page-level diagnostics	“Audit this site and prioritize the technical issues most likely to affect organic visibility.”
LOCAL_BUSINESS	Listings, reviews, locations, and local-market research	“Compare highly rated independent cafés around Lyon Part-Dieu.”
DOMAIN_ANALYTICS	Technology and domain intelligence	“Identify this site's technology stack and notable domain signals.”
CONTENT_ANALYSIS	Mentions, sentiment, topics, and content research	“Find recent brand mentions and group them by topic and sentiment.”
ECOMMERCE	Products, sellers, pricing, and shopping research	“Compare visible sellers and prices for this product category.”
AI_VISIBILITY	LLM responses, mentions, citations, and GEO research	“Measure which brands and sources are cited in AI answers for this topic.”

Be specific about country, language, search engine, date range, and result limit. Focused prompts are faster, easier to verify, and less likely to trigger several tool calls.

Authentication and privacy

Your MCP client authenticates to Apify with your personal Apify API token. The managed upstream account remains inside the Actor configuration and cannot be replaced through request headers or query parameters.

The Actor forwards each tool request in memory, returns the result over MCP, and does not persist live research results to a dataset. It also masks managed credentials in errors and logs. Save any result you need in your own project or workflow.

For least-privilege operation, create a dedicated Apify token for this connector and revoke it when it is no longer needed. A token embedded in a URL should be treated like a password.

Input

Connect your AI assistant with the Streamable HTTP endpoint shown above instead of starting a conventional Actor run. The optional target, location, language, and examplePrompt fields in the Input form exist only to render published Example pages. They do not configure the Standby MCP server or get forwarded to tool calls; each tool receives its actual parameters through the MCP conversation.

Pricing

SEO & GEO MCP uses Pay per Event. The primary billable event is Tool Read. One Tool Read represents one non-empty scalar data point read from the useful SEO or GEO payload returned to your MCP client. A tool call is the request; a Tool Read is one returned value, so a single tool call can produce zero, one, or many Tool Reads. For example, one keyword, search-volume value, CPC value, ranking position, backlink field, business attribute, product price, or AI-visibility metric counts as one Tool Read. JSON containers, response bookkeeping, null or empty values, errors, and MCP protocol traffic do not count.

The Free-plan rate is $0.005 per Tool Read ($5 per 1,000 data points read). See the live Pricing tab for the full table and automatic Apify-plan discounts.

A successful tool response with no data points is not charged. Initialization, tool discovery, malformed requests, authentication failures, upstream errors, timeouts, rate limits, and usage-limit rejections are also not charged. One AI prompt can cause several tool calls and return many Tool Reads, so use focused prompts, result limits, and an Apify spending limit when you need a hard cost ceiling.

Results and error handling

Tool output is returned directly to the connected LLM. The Actor's Output tab links to the connection guide, MCP endpoint, OpenAPI document, and health check. Public Task pages can display schema-based response examples, but the Actor does not store your live MCP results.

Upstream failures are converted into readable MCP tool errors instead of crashing the server. A successful result that reaches the Apify charge limit is still returned; subsequent tool calls receive a usage-limit message until the spending limit is increased.

Troubleshooting

• Unable to connect: verify that the URL begins with https://, ends at /mcp before the query string, and contains a current Apify token in place of the full uppercase placeholder.
• Opening /mcp stays open or shows no page: this is expected. The endpoint keeps a lightweight compatibility event stream open for MCP clients; JSON-RPC requests still use POST automatically.
• Claude asks for OAuth details: leave OAuth Client ID and OAuth Client Secret empty. The token in the URL is the authentication method.
• The first request is slow: allow 5–15 seconds for a cold Standby container to start, then retry once.
• Usage limit reached: increase the Apify run spending limit before making another call.

The URL https://mcp.apify.com?tools=mrbridge/seo-geo-mcp is not the direct endpoint for this product's internal tool catalog. That gateway can expose an Actor as an Actor-running tool, but it does not proxy this dedicated Standby /mcp server. Use the mrbridge--seo-geo-mcp.apify.actor/mcp URL documented above.

For support, use the Actor's Issues tab.

Frequently asked questions

Do I need a separate SEO data account?

No. The Actor owner manages the underlying service account. You connect with your Apify API token and pay for Tool Reads through Apify.

What counts as a Tool Read?

Each non-empty scalar data point inside the useful returned research payload counts as one Tool Read. A keyword, URL, search volume, CPC, ranking position, referring-domain value, review field, product price, or AI citation is one Tool Read. Structural JSON objects and arrays, response metadata, null values, and empty strings do not count.

Are failed calls charged?

No. Tool Read events are recorded only for useful values inside a confirmed successful result. MCP initialization, discovery, malformed requests, empty results, upstream failures, and rejected calls do not create a Tool Read charge.

Do I need to select or configure tools?

No. The complete catalog is exposed automatically. Your AI client discovers the available tools and chooses the appropriate one for each request.

Where are my results stored?

They are returned directly to your MCP client and are not saved to an Actor dataset. Save important results in your own workflow.

Responsible use

Use the tools only for lawful research and follow the terms that apply to Apify and the underlying data sources. Data coverage, freshness, regional availability, and individual endpoint limits can vary. Avoid placing personal, confidential, or regulated information in prompts unless your workflow is authorized to process it.

Built and maintained by MrBridge.