@seoasist/mcp

@seoasist/mcp

MCP server for SEOAsist. Lets Claude (Desktop, Code, claude.ai), ChatGPT, Cursor and any MCP client read your audits, open AI fixes (GitHub PRs), manage Pixel rules, keywords and blog content, and check AI-search visibility.

Option A: remote endpoint (no install, recommended)

https://seoasist.com/api/mcp speaks Streamable HTTP with OAuth 2.1. In claude.ai, Claude Desktop, ChatGPT, Cursor or VS Code add it as a connector; the SEOAsist sign-in opens and you pick the organization and permissions. No key copying.

# Claude Code (sign in with /mcp on first use)
claude mcp add --transport http seoasist https://seoasist.com/api/mcp

# servers / CI: API key instead of sign-in (SEOAsist → Settings → API keys)
claude mcp add --transport http seoasist https://seoasist.com/api/mcp --header "Authorization: Bearer sa_live_..."

Option B: stdio (this package)

{
  "mcpServers": {
    "seoasist": {
      "command": "npx",
      "args": ["-y", "@seoasist/mcp"],
      "env": { "SEOASIST_API_KEY": "sa_live_..." }
    }
  }
}

The package is a bridge to the remote endpoint, so the tool list always matches the server. Override the endpoint with SEOASIST_MCP_URL.

Tools

get_account, list_sites, get_site, start_crawl, get_issues, create_fix, list_fixes, list_pixel_rules, add_pixel_rule, delete_pixel_rule, get_keywords, add_keywords, list_content, get_content, create_blog_idea, approve_content, publish_content, get_brand, submit_article, get_backlinks, list_backlinks, find_link_opportunities, list_outreach, add_outreach, update_outreach, list_competitors, add_competitor, get_content_gap, get_head_to_head, get_todo, get_agent_tasks, complete_agent_task, log_activity, get_geo, get_monitors, get_ai_access, get_llms_txt, list_notifications, mark_notifications_read, list_reports.

Prompts

seo_round, content_from_gap, backlink_outreach, agent_tasks, weekly_report: ready-made workflows that show up in the client's prompt / slash-command menu.

Write tools need a key with the write scope. Rewrites of existing pages (page_update) can't be published live through the API; only blog posts.