SEO Perception MCP

This repository lists the hosted SEO Perception MCP server in MCP directories. It contains documentation and client configuration only. There is nothing to install or run locally: the server runs at https://seoperception.com/mcp.

SEO Perception stores weekly Google Search Console facts, a crawl of your site, and Possibilities (a prioritized fix list per URL). The MCP server lets your AI assistant read that same workspace and draft the next edit on a page, based on stored evidence instead of guesses.

At a glance

Related MCP server: mcp-server-gsc

Plan

Start with a 7-day Starter trial (MCP included). After the trial, OAuth, personal tokens, and the MCP endpoint need an active Starter, Pro, Business, or Enterprise plan. See pricing.

Tools

Nine tools read data SEO Perception has already collected. They never call Google live. seoperception_update_possibilities is the only write: it marks existing Possibilities done or ignored, and only when the connection includes mcp:possibilities. A connection with only mcp:read cannot change anything. OAuth Connect asks for both scopes. A personal token can close Possibilities only if you turn that on when you create it. Tokens you already created stay read-only.

Most tools take a siteId. Ask the assistant to list your sites first and it will pick it up.

Setup

Clients that support OAuth open a browser sign-in the first time they connect. No token needed.

If your client does not support OAuth, sign in to SEO Perception, open Account > MCP, create a personal access token (shown once), and store it as the environment variable SEOPERCEPTION_MCP_TOKEN. Then use the "token" variant of the config.

Cursor

Install the SEO Perception plugin from the Cursor Marketplace (once listed), or add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "seo-perception": {
      "url": "https://seoperception.com/mcp"
    }
  }
}

Cursor shows a sign-in prompt for the server. Token variant:

{
  "mcpServers": {
    "seo-perception": {
      "url": "https://seoperception.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SEOPERCEPTION_MCP_TOKEN}"
      }
    }
  }
}

Claude.ai and Claude Desktop (connectors)

1. Open Settings > Connectors.

2. Choose Add custom connector.

3. Name: SEO Perception. URL: https://seoperception.com/mcp.

4. Click Add, then Connect and approve the SEO Perception sign-in.

Custom connector availability depends on your Claude plan.

Claude Code

claude mcp add --transport http seo-perception https://seoperception.com/mcp

Then run /mcp inside Claude Code and choose Authenticate.

VS Code (GitHub Copilot agent mode)

Add to .vscode/mcp.json in your project, or run MCP: Add Server from the Command Palette and pick HTTP:

{
  "servers": {
    "seo-perception": {
      "type": "http",
      "url": "https://seoperception.com/mcp"
    }
  }
}

VS Code starts the OAuth sign-in when the server first connects.

Windsurf (Devin Desktop)

Add to mcp_config.json (~/.config/devin/mcp_config.json on current builds, ~/.codeium/windsurf/mcp_config.json on older Windsurf builds):

{
  "mcpServers": {
    "seo-perception": {
      "url": "https://seoperception.com/mcp"
    }
  }
}

Sign in when the server shows Needs auth, or use the token variant with a headers block as in the Cursor example.

Cline

In the Cline panel open MCP Servers > Remote Servers, enter the name seo-perception, URL https://seoperception.com/mcp, transport Streamable HTTP, then Add Server. Or edit cline_mcp_settings.json:

{
  "mcpServers": {
    "seo-perception": {
      "type": "streamableHttp",
      "url": "https://seoperception.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Set "type": "streamableHttp" explicitly; without it Cline falls back to the legacy SSE transport. See llms-install.md for step-by-step instructions an agent can follow.

Lovable

1. Open Connectors, click +, choose MCP server.

2. Server name: SEO Perception. URL: https://seoperception.com/mcp.

3. Keep OAuth, click Add & authorize, and approve the sign-in.

Any other MCP client

URL:            https://seoperception.com/mcp
Transport:      Streamable HTTP
Authorization:  OAuth 2.1 (discovered via WWW-Authenticate), or Bearer <your MCP token>

Example prompts

• "List my SEO Perception sites and tell me which data is freshest."

• "Summarize the strongest gains and losses for my site using stored data."

• "Show the highest-priority open SEO opportunities and explain the evidence."

• "Use SEO Perception to find the biggest losing keywords on /pricing and suggest concrete content changes to recover them."

• "Find non-branded queries in positions 5 to 20 with at least 50 impressions that are missing from their landing page."

• "Find keyword cannibalization and recommend which page should be preferred."

• "Find the biggest content and snippet gaps, then suggest rewrites that match the losing keywords."

• "Suggest internal links and natural anchor text for pages with ranking potential."

• "Which pages show meaningful content decay?"

• "Mark possibility 42 done after the draft is in the file."

Security and data boundary

• Your sites only. Every tool is limited to websites on the signed-in account.

• One optional write. Closing a Possibility does not edit the website, call Google, or start a recrawl. Done can come back on the next crawl. Ignore is permanent and needs a reason. A change by issue type or URL previews until confirm is true, and never closes more than 25 rows at once.

• No live Google calls. Tools read the weekly Search Console data, crawl, and prioritized fix list SEO Perception has already stored. Collection happens in the product's own sync, not inside a tool call.

• Scopes. mcp:read is required. mcp:possibilities is optional and is what allows closing to-dos. OAuth Connect asks for both. Allow both on the consent screen if the editor should be able to close a to-do. A client that requests only mcp:read stays read-only. A personal token stays read-only unless you enable closing when you create it.

• Tokens, not passwords. Never put your login password or session cookie in an MCP config. Create and revoke personal access tokens under Account > MCP.

• Your client's model provider. Your MCP client may send returned results to its model provider. Treat them as sensitive site analytics.

Troubleshooting

• 401: sign in again, or create a new token under Account > MCP and update SEOPERCEPTION_MCP_TOKEN.

• 403 paid_plan_required: MCP needs a plan that includes it (see Plan above).

• 429: wait for the retry time in the response.

• Empty lists: usually no stored data yet for that site.

Links

• Docs and setup: https://seoperception.com/mcp-integration

• Website: https://seoperception.com

• Pricing: https://seoperception.com/pricing

• Privacy: https://seoperception.com/privacy

• Support: https://seoperception.com/contact

• Server card: https://seoperception.com/.well-known/mcp/server-card.json

• Official MCP Registry: com.seoperception/mcp

About this repository

This repo holds only listing metadata (README, server.json, glama.json, llms-install.md, Cursor plugin manifest, logo). The SEO Perception application and MCP server source code are not open source and are not part of this repository.

Made by Larsik Corp (Lars Koudal). Documentation and configuration files are released under the MIT License. "SEO Perception" and the logo are trademarks of Larsik Corp. Google and Search Console are trademarks of Google LLC; SEO Perception is not affiliated with or endorsed by Google.