SEOforGPT MCP
About
AI visibility MCP for agencies and marketing teams to audit brand visibility in AI answers, monitor competitors and cited sources, and fix GEO gaps.
Details
- Author
- Unknown
- Categories
- Marketing, Knowledge Base, Other
Jump to
Use this page to connect SEOforGPT to Claude, understand what the hosted MCP gives the assistant, and choose the right fallback when you need the Public API or local package.
Need help choosing the right outcome or workflow?Open the AI visibility MCP product guide.
SEOforGPT publishes one hosted remote MCP endpoint. Claude is the primary documented setup, and compatible clients use the same URL when they support remote MCP.
OAuth with your normal SEOforGPT account; no pasted API key for the standard Claude flow.
Streamable HTTP on POST /mcp. This is not an older /sse/ endpoint.
The assistant sees the same projects, reports, quotas, and plan gates as the web app.
Use the connector URL from the top of this page. These are the only steps most users need.
Reconnecting. If the connector stops working, disconnect and add it again in Claude, or sign out and back into SEOforGPT from the authorization step.
Use normal language. Claude chooses tools as needed.
Use SEOforGPT. First list my projects and ask me which one to use.
Use SEOforGPT for the project I choose. Show me whether visibility is getting better or worse, then summarize the latest report.
Use SEOforGPT for the selected project and inspect my biggest competitor: where they win, which models mention them, and what sources cite them.
Use SEOforGPT to create a client brief for the project I choose with trend, competitor signal, losing prompts, cited domains, and 3 next actions.
Use SEOforGPT to check website readiness for the project I choose and turn it into a checklist.
Use SEOforGPT for the project I choose. Ask whether I want agent-found targets or sources AI already trusts, then retrieve that outreach list.
Once you are connected, use plain English in Claude. Pick the brand workflows for your own site, or the agency workflows when you manage client workspaces.
See whether your AI visibility is improving or declining before reading the full report.
Best for: Weekly brand monitoring and leadership updates.
Use SEOforGPT. First list my projects and ask me which one to use. Then show visibility trends for the selected project and summarize what changed versus the prior report.
Drill into the competitor that is winning prompts without dumping the whole report.
Best for: Competitive reviews and positioning work.
Use SEOforGPT for the project I choose. Find the strongest competitor, inspect their detail, and explain where they win, which models mention them, and what I should do next.
Use your visibility findings to create content that is ready for your brand to become visible in AI answers.
Best for: Content teams ready to publish AI-optimized content.
Use SEOforGPT on my selected project. Review the visibility findings, choose the strongest content opportunity, then use SEOforGPT to generate a brand-ready article designed to improve visibility in AI answers.
Run the readiness audit and turn it into a prioritized fix list your team can actually work through.
Best for: GEO audits, technical SEO reviews, and implementation planning.
Use SEOforGPT to check website readiness for the project I choose. Then give me the top fixes in priority order with a short reason for each.
Bundle trend, competitor signal, cited domains, losing prompts, and next actions in one client-ready view.
Best for: Monthly reporting and client check-ins.
Use SEOforGPT. List my client workspaces, ask which client to use, then create a client brief with trend, biggest competitor signal, cited domains, losing prompts, and 3 next actions.
Create a read-only report link the client can open without exposing the full workspace.
Best for: Client reporting handoff and async updates.
Use SEOforGPT for the client project I choose. Check account status, create a 30-day share link for the latest completed visibility report, and summarize what the client should look at first.
List clients, check quota/access, and identify which accounts need attention first.
Best for: Agency operations and account prioritization.
Use SEOforGPT to list my client workspaces. For each active client, check account status and tell me which ones need a visibility review, content action, or quota attention.
Run a one-off experiment for a brand that is not the one already saved in the project.
Best for: Agencies, pilots, prospecting, and one-off experiments.
I want to test a different brand with SEOforGPT. Ask me for the project, the brand name, and the prompts I want to test, then run the custom visibility check and summarize the result.
The hosted connector is tool-only in v1. Each tool maps to the same capabilities as in the app.
List projects so Claude can ask which one to use.
Run saved-project or custom-brand visibility workflows.
Fetch summary, raw, or agent-safe full visibility report data.
Show whether visibility score and appearance rate improved or declined.
Pull agent-safe competitor slices; summary omits raw answers.
Inspect one competitor with threat, model share, winning prompts, categories, and sources.
Create an agency-ready brief with trend, competitor, citation, prompt, and next-action signals.
Retrieve agent-found outreach targets or sources AI already trusts, with pagination and no pitch drafts.
Fetch one raw provider answer and citations for drill-down.
Create a public read-only brand visibility report link.
List agency client and pitch workspaces with billing and quota context.
Check plan, quota, workspace status, and feature access.
Publish a generated blog article to the connected blog; update briefs are not publishable as new posts.
Return a monthly persisted calendar with dates and reasons; poll generation or explicitly retry a completed empty month.
Generate routed content opportunities with content_action routing and skipped_topics for already-covered pages.
Generate structured content or existing-page update briefs; pass suggestion metadata for optimize_existing_url items.
Three surfaces share the same backend. Step-by-step setup for chat is in Connect & use (Claude). Notes for other chat tools are in Other assistants. Pick another surface when your workflow needs it:
MCP-capable assistants: same OAuth URL and tools as the app (we document Claude first). No API key in the assistant for the standard OAuth path.
Scripts, CI, cron, and direct HTTP integrations. Authenticate with a user API key or JWT.
Claude Desktop, Claude Code, or Cursor with npx and an API key. Same tools via Public API; for developers and power users.
The connector uses your existing SEOforGPT account and projects. There is no separate connector account.
- run_visibility consumes visibility quota.
- generate_content consumes content quota. For expand-vs-new decisions, call suggest_content_topics first and preserve its content_action metadata.
- publish_to_cms requires an active blog connection and an article; existing-page update briefs cannot be published as new posts.
- create_share_link requires report-sharing entitlement.
- check_website_readiness remains plan-gated.
- Read-oriented tools such as list_projects, get_visibility_report, get_visibility_trends, get_competitor_detail, get_client_brief, get_outreach_targets, list_client_workspaces, and get_account_status do not consume generation quota in the same way.
The hosted connector is a transport and auth layer on top of Public API v1. The API is what scripts and integrations call directly.
OAuth + managed connector key (assistant)
Chat in MCP-capable clients (Claude documented first)
For route-level HTTP details, seeAPI documentation.
Advanced local fallback: for Claude Desktop, Claude Code, or Cursor, you can run the published npm package over stdio with an API key from Settings -> API keys. This is not the default path for most users.
{ "mcpServers": { "seoforgpt": { "command": "npx", "args": ["-y", "@seoforgpt/mcp"], "env": { "SEOFORGPT_API_KEY": "sgpt_your_key_here" } } } }
Cursor uses the same shape in.cursor/mcp.json.
Transport note. This server speaks Streamable HTTP on POST /mcp. Some clients or tutorials still reference an SSE URL ending in /sse/. If your client only supports that older shape, it may not connect until it supports Streamable HTTP end to end. Use the REST API or an HTTP/OpenAPI action as a fallback.
For connector setup, authentication, and feature availability, follow the documentation for the assistant you are using. SEOforGPT only controls this endpoint and your account.
Still stuck?Emailhey@seoforgpt.iowith the product you are wiring and a short description of the error or missing field. We will point you to the right path (MCP URL, REST key, or Action schema).
Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.
Let AI clients add payments to your website. Create checkout pages, events and forms and embed them on your site in minutes.
Airefs monitors your visibility in AI answers then creates the articles, answers and earned mentions that influence them.
Creative intelligence from your ad accounts, inside your AI assistant.
Official remote MCP server for Canvora (canvora.ai): turn any idea, URL, doc, or PDF into on-brand visuals – carousels, posts, decks, and infographics in 100+ formats, native in 150+ languages. Brand kits, localization, PDF/PPTX export. Free tier. npx @canvora/cli
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





