@seoquantum/mcp

Official MCP server for SEOQuantum — drive SEO content optimization from Claude Code, Codex, Claude Desktop or Cursor.

Connect (1 command)

npx @seoquantum/mcp login

The browser opens: sign in, pick the workspace, done. A dedicated key is provisioned automatically and stored in ~/.seoquantum/config.json (permissions 0600). No key to copy, no file to install.

Client configuration

Claude Code

claude mcp add seoquantum -- npx -y @seoquantum/mcp

With several workspaces, pin one: append --profile <name> (printed by login).

Claude Code / Cursor / Claude Desktop — .mcp.json

{ "mcpServers": { "seoquantum": { "command": "npx", "args": ["-y", "@seoquantum/mcp", "--profile", "<name>"] } } }

Codex — ~/.codex/config.toml

[mcp_servers.seoquantum]
command = "npx"
args = ["-y", "@seoquantum/mcp", "--profile", "<name>"]

<name> is the workspace profile printed by login (omit --profile with a single workspace). Avoid pinning a version (@seoquantum/[email protected]): the client would keep an outdated server.

Switch workspace

Run npx @seoquantum/mcp login again (multiple profiles coexist). Pin a specific profile with --profile <name> (also via SEOQUANTUM_PROFILE).

Exposed tools

analyze_page, get_brief, list_pages, list_opportunities, get_page, get_recommendations, list_analyses, run_analysis, get_analysis, run_optimization, get_optimization, run_citability, get_citability.

Built for LLM agents:

• analyze_page runs an analysis, waits and returns the recommendations in one call. Without a page URL it launches a new brief, which uses 1 page of your workspace quota: the assistant asks for your confirmation first (confirm_new_brief), and it is refused once the page quota is reached.
• get_analysis / get_optimization wait for the result (wait_seconds, default 40 s), so the model does not spend a turn per status check.
• get_brief gives the writing material, even for a new brief with no content yet: semantic field with target counts, SERP (top titles, people also ask, related searches), competitor benchmarks, and the intent brief when generated in SEOQuantum.
• Every result carries a summary to relay, an app_url to open the page in SEOQuantum, and a next hint; get_optimization reports the score change.
• get_recommendations is compact by default (failed checks + terms to fix, by priority); pass detail: "full" for the raw data.
• Failed analyses carry error_code and retryable.
• Scores state what was scored (provenance.scored_content: live_page or draft).
• run_optimization is free (the workspace needs article quota left); resubmitting identical content usually returns the same optimization (rescore: true forces a new scoring).
• list_pages is compact by default (20 pages); pass detail: "full" for all fields. Each page carries its Google Search Console data (clicks, impressions, position, potential clicks, segment; with detail: "full", the previous period and deltas) over gsc_period days (default 28).
• list_opportunities ranks the pages to optimize first by Search Console potential clicks, by segment: quick_wins, strategic, at_risk, maintenance.
• get_page with include_content: true returns the current content (H1, meta tags, HTML), exactly the version scored in the SEOQuantum editor: the assistant reads it before rewriting.
• run_citability / get_citability (free): GEO citability of a scored optimization — can AI engines (ChatGPT, Perplexity, AI Overviews) quote each passage as-is? Returns the score, the passages to improve in reading order with their problems and guidance, and a section-by-section map. get_optimization carries a short citability summary.

Full spec: https://app.seoquantum.com/api/v1/openapi

Prompts

Ready-made workflows you launch yourself; the assistant then chains the tools.

| Prompt | Arguments | What it does | |---|---|---| | optimize_page | keyword, url | Optimizes an existing page for organic search and AI answer engines (SEO + GEO): SEO fixes, rewrite, SEO and GEO citability scores, what the text alone cannot fix. Without url: writes a new article | | write_article | keyword | Writes a new article from a SEOQuantum brief, optimized for SEO + GEO (asks before using 1 page of quota) | | plan_topic_cluster | topic | Plans a pillar page and its cluster pages from your existing pages (no quota used) | | prioritize_pages | segment (optional) | Picks the pages to optimize first from Search Console data |

• Claude Code: type / and pick seoquantum:<prompt> (MCP), or type /mcp__seoquantum__optimize_page running-shoes https://example.com/page. Arguments are separated by spaces and quotes are not supported. optimize_page rejoins a multi-word keyword typed without URL (/mcp__seoquantum__optimize_page dog insurance); otherwise, simply ask in plain language (the tools are the same).
• Claude Desktop: + button under the chat box, then the SEOQuantum server's prompts.
• Other clients: Cursor supports MCP prompts; Codex does not document them. A client without prompt support keeps every tool: just ask, e.g. “optimize this page for AI search”.

Options

| Flag / env | Purpose | |---|---| | --profile <name> / SEOQUANTUM_PROFILE | Workspace profile to use | | --base <url> / SEOQUANTUM_API_BASE | Override the API base | | SEOQUANTUM_API_KEY | Key that takes precedence (backward compatibility) | | login --no-browser | Do not open the browser, print the URL |

Node 18+ required. Revoke a key anytime from your workspace settings.