Connect SEOforGPT to your AI agent

    Connect your AI agent, sign in to SEOforGPT, and use the same tools as the web app directly on your favourite agent.

    Sign in to SEOforGPTOpen Claude

    Recommended setup

    Paste this URL into Claude’s Remote MCP server URL field and leave Advanced settings empty.

    Remote MCP server URL

    https://www.seoforgpt.io/mcp
    1. 1. In Claude, go to Customize -> Connectors -> + -> Add custom connector.
    2. 2. Name it SEOforGPT.
    3. 3. Paste the URL above into Remote MCP server URL.
    4. 4. Leave Advanced settings empty.
    5. 5. Click Add, then Connect.
    6. 6. Sign into SEOforGPT and approve access.

    Documentation

    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.

    Skip to Claude setup · Other assistants

    Overview

    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.

    URL
    https://www.seoforgpt.io/mcp
    Authentication
    OAuth with your normal SEOforGPT account; no pasted API key for the standard Claude flow.
    Transport
    Streamable HTTP on POST /mcp. This is not an older /sse/ endpoint.
    Data
    The assistant sees the same projects, reports, quotas, and plan gates as the web app.

    Connect & use (Claude)

    Use the connector URL from the top of this page. These are the only steps most users need.

    1. 1In Claude, go to Customize -> Connectors -> + -> Add custom connector.
    2. 2Name it SEOforGPT, then paste the URL from the top of this page into Remote MCP server URL.
    3. 3Leave Advanced settings empty unless your IT team gave you specific instructions.
    4. 4Click Add, then Connect, sign in to SEOforGPT when prompted, and approve access.
    5. 5In chat, ask Claude to use SEOforGPT. Start by listing projects, then pick a project for visibility, reports, or content. See Tools for what each tool does.

    Reconnecting. If the connector stops working, disconnect and add it again in Claude, or sign out and back into SEOforGPT from the authorization step.

    Best first prompts

    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.

    Example workflows

    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.

    Brand workflows

    Check visibility movement

    See whether your AI visibility is improving or declining before reading the full report.

    Best for: Weekly brand monitoring and leadership updates.

    Prompt to paste

    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.

    Inspect one competitor

    Drill into the competitor that is winning prompts without dumping the whole report.

    Best for: Competitive reviews and positioning work.

    Prompt to paste

    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.

    Turn the data into a content brief

    Use your visibility findings to decide what to publish next, without bouncing between the app and your writing tool.

    Best for: Content teams deciding what to write next.

    Prompt to paste

    Use SEOforGPT on my selected project. Review the visibility findings and give me 3 article ideas with the strongest opportunity behind each one.

    Check site readiness for AI search

    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.

    Prompt to paste

    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.

    Agency workflows

    Create a client visibility brief

    Bundle trend, competitor signal, cited domains, losing prompts, and next actions in one client-ready view.

    Best for: Monthly reporting and client check-ins.

    Prompt to paste

    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.

    Prepare a shareable client report

    Create a read-only report link the client can open without exposing the full workspace.

    Best for: Client reporting handoff and async updates.

    Prompt to paste

    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.

    Review every client workspace

    List clients, check quota/access, and identify which accounts need attention first.

    Best for: Agency operations and account prioritization.

    Prompt to paste

    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.

    Test a prospect or custom prompt set

    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.

    Prompt to paste

    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.

    Tools

    The hosted connector is tool-only in v1. Each tool maps to the same capabilities as in the app.

    Tool
    What it does
    list_projects
    List projects so Claude can ask which one to use.
    run_visibility
    Run saved-project or custom-brand visibility workflows.
    get_visibility_report
    Fetch summary, raw, or agent-safe full visibility report data.
    get_visibility_trends
    Show whether visibility score and appearance rate improved or declined.
    get_competitor_intelligence
    Pull agent-safe competitor slices; summary omits raw answers.
    get_competitor_detail
    Inspect one competitor with threat, model share, winning prompts, categories, and sources.
    get_client_brief
    Create an agency-ready brief with trend, competitor, citation, prompt, and next-action signals.
    get_provider_answer
    Fetch one raw provider answer and citations for drill-down.
    create_share_link
    Create a public read-only brand visibility report link.
    list_client_workspaces
    List agency client and pitch workspaces with billing and quota context.
    get_account_status
    Check plan, quota, workspace status, and feature access.
    publish_to_cms
    Publish an existing generated content item to the connected CMS.
    check_website_readiness
    Run the GEO / LLM-readiness assessment.
    generate_content
    Generate blog, LinkedIn, or thread content.
    suggest_prompts
    Advanced crawl-based prompt generation.

    When to use what

    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:

    Surface
    Best for
    Hosted MCP (remote)
    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.
    Public API v1
    Scripts, CI, cron, and direct HTTP integrations. Authenticate with a user API key or JWT.
    Local MCP (stdio)
    Claude Desktop, Claude Code, or Cursor with npx and an API key. Same tools via Public API; for developers and power users.

    Account & quotas

    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.
    • publish_to_cms requires an active CMS connection and existing generated content.
    • 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, list_client_workspaces, and get_account_status do not consume generation quota in the same way.

    Relationship to the Public API

    The hosted connector is a transport and auth layer on top of Public API v1. The API is what scripts and integrations call directly.

    Hosted MCP
    Public API v1
    OAuth + managed connector key (assistant)
    JWT or visible user API key
    Chat in MCP-capable clients (Claude documented first)
    Scripts, CI, cron, HTTP
    Hosted MCP (Streamable HTTP)
    REST JSON

    For route-level HTTP details, see API documentation.

    Advanced: local package

    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.

    Other assistants

    The hosted endpoint at https://www.seoforgpt.io/mcp is the same URL documented for Claude. If another assistant lets you add a remote MCP server URL, paste that address. Whether it works depends on that product's rollout, region, and transport support. If a surface only supports HTTP actions instead of MCP, use the Public API or wire an OpenAPI-based HTTP action in the product you use. We do not ship a second MCP stack for individual vendors.

    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? Email hey@seoforgpt.io with 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).