Connect SEOforGPT to your AI agent

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.

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.

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.

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 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.

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.

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.

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.

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.

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.

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:

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. 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.
• add_custom_prompts saves only to an onboarded project; testNow queues background testing for the added prompts.
• save_content_version does not call a model or consume content-generation quota.
• list_content_library and get_content are read-only and do not consume content-generation quota.
• 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.

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.

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.