---
title: "SEO MCP Server for Agencies | SEOPro AI"
description: "Turn live Search Console insight into prioritized work, generated content, CMS publishing, indexing, and AI-referral measurement from Claude, ChatGPT, and other MCP clients."
url: https://seoproai.co/mcp
---

# SEOPro AI MCP server

SEOPro AI ships a remote Model Context Protocol server at https://api.seoproai.co/api/mcp. Point Claude, ChatGPT or any MCP client at it and the assistant can read live Search Console data, plan content, generate and publish articles, request indexing, and measure AI referrals — without leaving the chat.

## Connect

- Endpoint: https://api.seoproai.co/api/mcp (streamable HTTP, stateless)
- Auth option 1 — API key: send `Authorization: Bearer sk_...`, created under Settings → API keys.
- Auth option 2 — OAuth 2.1 with PKCE, discovered from the RFC 9728 protected-resource metadata the endpoint advertises.
- Setup guides: /mcp/claude, /mcp/chatgpt, /mcp/openclaw, /mcp/hermes

## Tools

- list_websites (read) — List the websites in the user's account with the numeric website_id needed by every other tool.
- get_website_stats (read) — Total articles, keywords tracked, published posts and whether SEO autopilot is enabled.
- get_search_performance (read) — Google Search Console summary: clicks, impressions, CTR, average position, top keywords, AI-assistant traffic and device/country breakdowns.
- get_top_search_keywords (read) — Top search keywords with clicks, impressions, CTR and average position — useful for finding positions 5-15 quick wins.
- get_search_trends (read) — Monthly search-performance trends over the last N months to spot growth or decay.
- get_ai_search_traffic (read) — Traffic arriving from ChatGPT, Perplexity, Claude, Gemini and other AI assistants, broken down per source.
- run_seo_audit (write) — Technical audit of any URL: meta tags, headings, images, links, performance, content quality, security and social metadata, with a scored result.
- check_ai_citations (write) — Check whether ChatGPT, Claude, Gemini and Perplexity mention or cite a website when answering questions in its niche.
- get_backlink_profile (read) — Backlink totals, unique sources, available Link Credits and the most recent earned backlinks.
- get_keyword_plan (read) — The scheduled keyword/content plan: planned keywords, their scheduled dates and statuses.
- generate_keyword_plan (write) — Generate an AI keyword/content plan, optionally guided by topic instructions and primary/secondary keywords.
- generate_article (write) — Start generating an SEO article for a target keyword. Returns immediately; generation takes 5-10 minutes in the background.
- get_article_status (read) — Article generation and publication status per date, used to poll a generation started by generate_article.
- list_articles (read) — List drafts and published articles newest first, optionally filtered by status.
- get_article (read) — Read a single article by blog_id, with the full HTML content on request.
- publish_article (external-write) — Publish an article to the connected CMS (WordPress, Shopify, Webflow and others), optionally as an unpublished draft.
- request_indexing (external-write) — Submit up to 50 URLs to Google and Bing for indexing. Requires the auto-indexing feature and explicit user confirmation.
- get_indexing_status (read) — Auto-indexing stats: how many URLs are indexed, pending or failed.

## Typical workflow

Call list_websites to get a website_id. Use get_search_performance and get_top_search_keywords to find opportunities, generate_keyword_plan to schedule them, and generate_article to start a draft. Poll get_article_status, read the result with get_article, then publish_article and request_indexing. Measure the outcome with get_ai_search_traffic and check_ai_citations.

## Machine-readable entry points

- Agent index: https://seoproai.co/llms.txt
- Full text of every public page: https://seoproai.co/llms-full.txt
- MCP server: https://api.seoproai.co/api/mcp
- OpenAPI description: https://api.seoproai.co/openapi.json