Hosted MCP (Streamable HTTP)

    Connect SEOforGPT to Claude with one URL

    The normal setup no longer needs npm, local builds, or a pasted API key. Add the hosted connector in Claude, sign into SEOforGPT, and start using the same visibility, competitor, readiness, and content workflows the app already uses. The endpoint is standard remote MCP (Streamable HTTP). Other assistants can use the same base URL when their OAuth client supports it. Read ChatGPT and OpenAI in the docs below for details.

    Sign in to SEOforGPTOpen Claude

    Recommended setup

    Paste this URL into Claude’s Add custom connector flow and leave Advanced settings empty.

    Connector URL

    https://www.seoforgpt.io/mcp
    1. 1. In Claude, click Add custom connector.
    2. 2. Paste the URL above.
    3. 3. Leave Advanced settings empty.
    4. 4. Click Connect.
    5. 5. Sign into SEOforGPT and approve access.

    Documentation

    Start with Connect & use (Claude) for the supported Claude flow. The hosted URL is the same remote MCP endpoint described in ChatGPT & OpenAI; we do not ship a separate MCP server for OpenAI. No API key is required for the standard Claude path.

    Overview

    The hosted connector is a remote MCP endpoint at https://www.seoforgpt.io/mcp. You sign in with your normal SEOforGPT account (OAuth). The assistant receives the same tools and data as the web app, subject to your plan and quotas. The transport is Streamable HTTP (POST /mcp) from the official MCP SDK. That matches OpenAI's Streamable HTTP MCP docs. It is not a separate /sse/ URL.

    One endpoint, many clients. SEOforGPT maintains this single hosted MCP. We do not ship a second codebase for other assistants. We document step-by-step setup for Claude below. Other hosts (e.g. ChatGPT) are supported by their products with remote MCP. See ChatGPT & OpenAI.

    You do not need npm, a local build, or a pasted API key for the standard Claude setup. Advanced users who want a local stdio client can still use the npm package with an API key. See Advanced: local package.

    Connect & use (Claude)

    1. In Claude, open Add custom connector and paste the connector URL from the top of this page.
    2. Leave Advanced settings empty unless your IT team gave you specific instructions.
    3. Click Connect, then sign in to SEOforGPT when prompted and approve access.
    4. In 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. Run the normal visibility check and explain the result simply.
    Use SEOforGPT for the selected project and show me the competitor picture, including gaps, sources, and citations.
    Use SEOforGPT to check website readiness for the project I choose and turn it into a checklist.
    Use SEOforGPT to draft a blog post about zero-click search for the selected project.

    ChatGPT and OpenAI

    OpenAI has been expanding support for MCP-style tool orchestration across ChatGPT and the API. Connector and MCP rollout varies by product, region, and account. Always check OpenAI's current docs. The hosted endpoint at https://www.seoforgpt.io/mcp is the same URL Claude uses; if your ChatGPT or developer console accepts a remote MCP server URL, paste that address. If a given surface does not accept MCP URLs yet, use this REST API or an OpenAPI schema (for example Custom GPT Actions). We are not shipping a separate ChatGPT MCP product or repo.

    Transport note. This server speaks Streamable HTTP on POST /mcp. OpenAI's Agents SDK documents Streamable HTTP for remote MCP; some ChatGPT examples still show an SSE URL ending in /sse/. If a surface only accepts that older shape, it may not connect until the client supports this transport end to end. Use this REST API or a Custom GPT Action as a fallback.

    Where to read OpenAI’s side. Start with the Apps SDK quickstart and the MCP and connectors guide on the OpenAI Platform docs. Those pages describe when MCP applies to ChatGPT connectors versus API-only flows, plus the authentication patterns OpenAI expects.

    Still stuck? Email mcp@seoforgpt.io with the product you are wiring (ChatGPT connector, API assistant, etc.) 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).

    Example workflows

    Once you are connected, use plain English in Claude. Below are end-to-end examples you can paste or adapt. Each one maps to the same tools as the web app.

    Get a visibility brief

    Run your normal SEOforGPT visibility check and get a short, useful briefing instead of raw data.

    Best for: Weekly checks, client updates, or fast decision-making.

    Prompt to paste

    Use SEOforGPT. First list my projects and ask me which one to use. Then run a visibility check and give me the 3 biggest takeaways on visibility, trend direction, and competitors.

    Understand the competitor picture

    Pull the richer competitor view: who shows up, which prompts you miss, and which source domains keep getting cited.

    Best for: Content strategy, competitive reviews, and board-level summaries.

    Prompt to paste

    Use SEOforGPT for the project I choose. Show me the competitor picture: who appears most, which prompts we miss, and which source domains or citations show up most often.

    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.

    Test a different brand or a 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, full, or raw visibility report data.
    get_competitor_intelligence
    Pull the competitor-focused slices from a full report.
    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). OpenAI / ChatGPT notes are in ChatGPT & OpenAI. 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.
    • check_website_readiness remains plan-gated.
    • Read-oriented tools such as list_projects, get_visibility_report, and get_competitor_intelligence do not consume generation quota in the same way.

    Team & Enterprise

    • Free, Pro, and Max users can add the connector themselves.
    • Team and Enterprise owners add the connector once for the workspace; members connect their own SEOforGPT account individually.

    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.