SEOPro AI

io.github.alpha-ai-labsPublished by GitHub account alpha-ai-labsv1.2.0Updated Oct 24, 2026

Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted SEO MCP server that turns Search Console data into audits, keyword plans, AI-written articles, CMS publishing and indexing requests.

What you can do
  • List websites and read account context, content stats and autopilot status
  • Pull Google Search Console performance, top keywords, monthly trends and AI-assistant referral traffic
  • Run technical SEO audits on any URL, check AI citations and review backlink profiles
  • Read and generate keyword/content plans, then start asynchronous article generation and poll status
  • List and read articles, publish approved drafts to a connected CMS, and submit URLs for indexing with status checks
When to use it
Useful for founders, marketers, consultants and agencies who manage one or many websites and want an assistant to move from Search Console insight to prioritized actions, generated content, publishing and indexing in one loop.
Requirements
A remote Streamable HTTP endpoint; no local runtime or package. An SEOPro AI account (the README mentions a paid seven-day trial offer), connected websites, Google Search Console for performance workflows, and a supported CMS connection for publishing. Authentication is required on every request: OAuth in interactive clients, or a revocable SEOPro AI API key as a bearer token.
Before you install
Publishing pushes content to a live CMS unless publish_as_draft is set, and indexing submits URLs to Google/Bing; both require an explicit confirmation argument and should follow user approval. Generating a keyword plan with replace_existing discards pending topics. Account data, website content and tool arguments go to the SEOPro AI backend, which records operational metadata. Keep API keys in the client's secret store, never in config files.

Installation

In SourceWeft

  1. Open SEOPro AI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.alpha-ai-labs%2Fseo-agent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "seopro-ai": {
      "type": "http",
      "url": "https://api.seoproai.co/api/mcp"
    }
  }
}

README

SEOPro AI Agent Plugin

Run the full SEO loop from your AI assistant:

Search Console insight → prioritized action → generated article → CMS publishing → indexing → measurable Google and AI-referral results.

SEOPro AI is a hosted remote MCP server for anyone responsible for website growth, from founders and small teams to in-house marketers, consultants, and agencies. It is distributed as a portable Agent Plugin. The implementation stays on SEOPro AI infrastructure; this repository contains the public connection metadata, setup guides, reusable SEO workflows, and security documentation.

[Agency operators reviewing an SEO workflow]

Connect

Install as an Agent Plugin

This repository conforms to Agent Plugins 1.0.0. Add or clone the repository through a compatible client's plugin installation flow. The client discovers:

text
seoproai-mcp/├── plugin.json                   # Agent Plugins manifest├── mcp.json                      # Agent Plugins MCP config├── .claude-plugin/plugin.json    # Claude plugin manifest├── .mcp.json                     # Claude plugin MCP config└── skills/    └── seoproai-operator/        └── SKILL.md
  • plugin.json identifies the portable package.
  • mcp.json declares the hosted Streamable HTTP server.
  • .claude-plugin/plugin.json and .mcp.json make the same package native to Claude Code and Cowork.
  • skills/seoproai-operator/ supplies safe SEO workflows and approval gates for one or many websites.

Agent Plugins 1.0.0 intentionally leaves remote authentication to the client. Complete OAuth in the client or keep a scoped SEOPro AI API key in its secret store. Never add credentials to mcp.json, plugin.json, or SKILL.md.

Clients that do not yet load Agent Plugins can use the manual setup below.

Connect manually

Remote MCP URL

text
https://api.seoproai.co/api/mcp

No server package or local runtime is required. Interactive clients use OAuth. Developer clients may use a revocable SEOPro AI API key as a bearer token.

Official MCP Registry identifier: io.github.alpha-ai-labs/seo-agent

ClientAuthSetup
ClaudeOAuthSettings → Connectors → Add custom connector → paste the URL → Connect
ChatGPTOAuthSettings → Apps & Connectors → Advanced/Developer mode → Create → paste the URL
CodexOAuthcodex mcp add seopro-ai --url https://api.seoproai.co/api/mcp, then codex mcp login seopro-ai
Claude CodeOAuth or API keyclaude mcp add --transport http seopro-ai https://api.seoproai.co/api/mcp
HermesAPI keyAdd the URL and environment-backed bearer header in ~/.hermes/config.yaml
OpenClawOAuth or API keyAdd a Streamable HTTP entry under mcp.servers; prefer OAuth or keep a static key in an environment variable
Cursor / WindsurfOAuth or API keyAdd a remote Streamable HTTP server in MCP settings

See client setup for copy-paste configurations and current caveats.

Three SEO workflows

1. Find website quick wins

text
Using SEOPro AI, list my websites. For [website], review the last 28 days ofSearch Console performance. Find queries ranking 5–15 with meaningfulimpressions, group them by page, and give me a prioritized action plan. Do notmake any changes.

2. Build and generate a content plan

text
Using SEOPro AI, review [client site]'s search performance and current keywordplan. Propose a four-week content plan around [service/topic]. Show me the planbefore creating it. After I approve it, create the keyword plan and generateonly the first article.

3. Review, publish, index, and measure

text
Using SEOPro AI, show me the draft for [article]. Check its title, metadescription, structure, and relevance to the target keyword. Do not publishuntil I explicitly approve the final draft. After approval, publish it, submitthe published URL for indexing, and give me a 30-day measurement checklist.

The complete prompt pack is in agency prompt pack.

Demo and example data

[Example connected Search Console performance view]

The Search Console image is an example connected performance view. Results vary by website.

What the server exposes

The server provides 18 narrowly scoped tools across:

  • Websites and account context.
  • Search Console summaries, keywords, trends, and AI-referral traffic.
  • Technical audits, AI citations, and backlink profiles.
  • Keyword/content planning and asynchronous article generation.
  • Draft review and explicit-confirmation CMS publishing.
  • Explicit-confirmation indexing requests and indexing status.

Read tools are annotated as read-only and non-destructive. Publishing and indexing are annotated as externally consequential and require an explicit confirmation argument on every call.

Privacy and security

  • Authentication is required for every MCP request.
  • OAuth and API-key access can be revoked.
  • Website ownership and subscription limits are enforced by the same backend routes used by the SEOPro AI dashboard.
  • Analytics records operational metadata such as tool name, success, latency band, auth method, and normalized client family. It never records credentials, tool arguments, article content, website content, or returned customer data.
  • The public repository contains no hosted-server source code or credentials.

Read SECURITY.md, architecture and data handling, and the SEOPro AI Privacy Policy.

Requirements

  • An SEOPro AI account. The current acquisition offer is a $1 seven-day trial.
  • Connected websites and, for search-performance workflows, Google Search Console.
  • A supported CMS connection for publishing workflows.

Start at seoproai.co/mcp.

Repository map

  • plugin.json — Agent Plugins 1.0.0 package manifest.
  • mcp.json — Portable Streamable HTTP MCP connection without embedded credentials.
  • .claude-plugin/plugin.json — Claude Code and Cowork plugin manifest.
  • .mcp.json — Claude-native remote HTTP connector configuration without embedded credentials.
  • server.json — Official MCP Registry metadata for the hosted endpoint.
  • docs/client-setup.md — Client-specific setup.
  • docs/agency-prompt-pack.md — Safe, reusable agency prompts.
  • docs/compatibility.md — Tested client/auth matrix.
  • docs/troubleshooting.md — Connection and tool-call diagnostics.
  • docs/architecture-and-data-handling.md — Trust boundary and analytics disclosure.
  • docs/directory-listing-copy.md — Canonical short and long listing descriptions.
  • docs/90-second-demo-script.md — Timed narration, capture plan, and privacy checklist.
  • docs/example-tool-results.md — Fictional sample data for screenshots and reviews.
  • assets/ — Public workflow and product-proof visuals.
  • skills/seoproai-operator/ — Portable Agent Skill for founders, small teams, in-house marketers, consultants, and agencies.
  • scripts/validate_agent_plugin.py — Schema, transport, package-boundary, and skill validation used by CI.

Support

Email [email protected] or open a GitHub issue without including credentials or customer data. Service availability: seoproai.co.

License

Documentation and repository assets are licensed under MIT. The hosted SEOPro AI service and its implementation remain proprietary and are governed by the Terms.

Source: README.md at commit b0ec8b7

Tools

18

list_websites

List Account Websites

List the websites in the user's SEOPro AI account. Returns each website's numeric website_id (needed by most other tools), URL, platform and autopilot status. Call this first.

Takes no parameters.

get_website_stats

Get Website Content Stats

Get content stats for a website: total articles, keywords tracked, published posts and whether SEO autopilot is enabled.

Parameterswebsite_idrequired

get_search_performance

Get Search Performance

Get the Google Search Console performance summary for a website: clicks, impressions, CTR, average position, top keywords, AI-assistant traffic sources and device/country breakdowns. Dates are YYYY-MM-DD; defaults to the last 30 days.

Parametersend_datestart_datewebsite_idrequired

get_top_search_keywords

Find Top Search Keywords

List the website's top search keywords with clicks, impressions, CTR and average position. Great for finding quick wins (positions 5-15 with high impressions). Dates are YYYY-MM-DD; defaults to the last 30 days.

Parameterslimitend_datestart_datewebsite_idrequired

get_ai_search_traffic

Measure AI Search Traffic

Show traffic the website receives from AI assistants and AI search (ChatGPT, Perplexity, Claude, Gemini, etc.): sessions, engaged pages and per-source breakdowns. Dates are YYYY-MM-DD; defaults to the last 30 days.

Parameterslimitend_datestart_datewebsite_idrequired

run_seo_audit

Run Technical SEO Audit

Run a technical SEO audit on any URL: meta tags, headings, images, links, performance, content quality, security and social metadata, with a scored result. Rate-limited for free accounts.

Parametersurlrequired

check_ai_citations

Check AI Citations

Check whether AI assistants (ChatGPT, Claude, Gemini, Perplexity) mention or cite a website when answering questions in its niche. Takes 1-3 minutes; results are cached for 7 days.

Parametersurlrequired

get_keyword_plan

Get Keyword Content Plan

Get the website's scheduled keyword/content plan: which keywords are planned, their scheduled dates and statuses.

Parameterswebsite_idrequired

generate_keyword_plan

Generate Keyword Content Plan

Generate an AI keyword/content plan for the website. Optionally guide it with topic instructions and comma-separated primary/secondary keywords. Can take a minute or two. Set replace_existing=true only after the user explicitly approves discarding the current plan's pending topics; that path also requires confirm_replace_existing=true.

Parameterswebsite_idrequiredprimary_keywordsreplace_existingsecondary_keywordstopic_instructionsconfirm_replace_existing

generate_article

Generate SEO Article

Start generating an SEO article for a target keyword. Returns immediately; generation takes 5-10 minutes in the background — poll get_article_status for the scheduled_date until it shows a blog. scheduled_date is YYYY-MM-DD and defaults to today (UTC). One article is generated per website per date; if that date already has an article the existing blog_id is returned. Counts toward the plan's monthly limit.

Parameterstopickeywordrequiredwebsite_idrequiredscheduled_date

get_article_status

Check Article Generation Status

Check article generation/publication status per date. Dates are YYYY-MM-DD and default to the current month. A date with has_blog=true and a blog_id means the article is ready to read via get_article.

Parametersend_datestart_datewebsite_idrequired

list_articles

List Website Articles

List the website's articles (drafts and published), newest first. Optionally filter by status (e.g. 'draft', 'published').

Parameterslimitstatuswebsite_idrequired

get_article

Review Article Draft

Read a single article by blog_id. By default returns metadata and a short excerpt; set include_content=true for the full HTML content.

Parametersblog_idrequiredinclude_content

publish_article

Publish Article to CMS

Publish an article to the website's connected platform (WordPress, Shopify, Webflow, etc.). Set publish_as_draft=true to push it as an unpublished draft in the CMS instead of going live. Before calling, show the user the article and destination and obtain explicit approval. Every call requires confirm_publish=true.

Parametersblog_idrequiredconfirm_publishpublish_as_draft

request_indexing

Request Search Engine Indexing

Submit up to 50 URLs for search-engine indexing (Google/Bing) via SEOPro AI auto-indexing. Requires the auto-indexing feature on the account. Show the exact URL list and obtain explicit user approval first; every call requires confirm_indexing=true.

Parametersurlsrequiredwebsite_idrequiredconfirm_indexing

get_indexing_status

Get Indexing Status

Get auto-indexing stats for the website: how many URLs are indexed, pending or failed.

Parameterswebsite_idrequired

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts