API and MCP documentation

    SEOforGPT Developers: build from your app or your agent

    Use the REST API for software integrations and automation. Use hosted MCP when you want Claude or another compatible assistant to run SEOforGPT tools through chat.

    Start here

    Pick the integration type first. Then use the endpoint only after you have the right authentication method.

    Building software, scripts, or internal tools

    1. 1. Create an API key in your SEOforGPT account.
    2. 2. Send it as a Bearer token from your server or job.
    3. 3. Call Public API v1 for projects, reports, analysis, and content.

    Connecting Claude or another MCP client

    1. 1. Add SEOforGPT as a custom connector in the MCP client.
    2. 2. Sign in with OAuth when the client asks for access.
    3. 3. Ask the assistant to list projects, run visibility, or fetch reports.

    Choose the right path

    Both paths access the same SEOforGPT product data. The difference is whether your integration is code-driven or assistant-driven.

    REST API

    Best for backend services, CI jobs, internal dashboards, and custom workflows where your code controls each request.

    Use when

    You need predictable HTTP routes, JSON responses, and API-key auth.

    First step

    Create an API key, then call the base URL with Bearer auth.

    Hosted MCP

    Best when an assistant should list projects, run visibility checks, fetch reports, or draft content from a conversation.

    Use when

    Your client supports remote MCP and can complete OAuth sign-in.

    First step

    Paste the URL into Claude’s Remote MCP server URL field.

    REST base URL

    https://www.seoforgpt.io/api/v1

    Remote MCP server URL

    https://www.seoforgpt.io/mcp

    What you can do

    The developer surfaces expose the core work your team already does in SEOforGPT.

    View all routes

    Read project context

    List projects and use saved brand, website, and competitor setup.

    GET /api/v1/projects

    Run visibility checks

    Start saved-project or custom-brand visibility workflows.

    POST /api/v1/analyze/project

    Fetch report data

    Pull latest, summary, full, or raw visibility report results.

    GET /api/v1/reports/latest

    Generate content

    Create AI-search-informed blog, LinkedIn, or thread drafts.

    POST /api/v1/generate-content

    Resources

    Use these when you need implementation details, machine-readable context, or account setup.

    Authentication

    REST uses Bearer tokens. Hosted MCP uses OAuth from the connector flow.

    Agent context

    Use llms.txt and index.md for crawler and assistant summaries.

    One MCP URL

    We publish one hosted MCP endpoint. Compatibility depends on the client.