SEOPro AI

What SEOPro AI MCP server does

SEOPro AI MCP server gives AI assistants access to an SEO workflow backed by the hosted SEOPro AI service. It can work with website and account context, inspect Search Console performance, identify keyword opportunities, and help organize actions by page or topic. The workflow also covers technical audits, AI-referral traffic, AI citations, and backlink profiles.

Content work includes keyword planning, content planning, and asynchronous article generation. Generated work can be reviewed before publication, then sent to a connected CMS after explicit approval. Published URLs can also be submitted for indexing, with indexing status available for follow-up. These capabilities support a complete sequence from search data to content production and post-publication measurement.

How it works

The repository provides public connection metadata, setup documentation, reusable workflows, and security information. The actual implementation runs on SEOPro AI infrastructure rather than in the repository. Clients connect to the hosted Streamable HTTP MCP endpoint at https://api.seoproai.co/api/mcp.

The SEOPro AI MCP server exposes 18 narrowly scoped tools. Read-only operations are marked as non-destructive. Publishing and indexing operations are treated as externally consequential and require an explicit confirmation argument on every call. This lets an agent prepare recommendations or drafts without making changes until the user approves the relevant step.

Setup and configuration

The SEOPro AI MCP server requires an SEOPro AI account. Connect a website to the account and connect Google Search Console for search-performance workflows. Publishing requires a supported CMS connection. The documented acquisition offer is a $1 seven-day trial.

Agent Plugin-compatible clients can install or clone the repository package and discover its MCP configuration. Clients without Agent Plugin support can add the remote URL manually. Interactive clients use OAuth; developer clients can use a revocable SEOPro AI API key as a bearer token. Authentication must be supplied for every MCP request, and credentials should remain in the client’s secret store rather than in repository configuration files.

Cursor and Windsurf can add the endpoint as a remote Streamable HTTP server. Claude, ChatGPT, and Codex setup paths are also documented, with Codex using its MCP add and login commands. The repository includes client-specific setup and troubleshooting documentation.

Tools and capabilities

The available tool groups cover:

• Website and account context
• Search Console summaries, keywords, and trends
• AI-referral traffic, AI citations, and backlink profiles
• Technical audits
• Keyword and content planning
• Asynchronous article generation
• Draft review
• CMS publishing after explicit confirmation
• Indexing requests and indexing status after explicit confirmation

Typical workflows include finding queries ranking in positions 5–15 with meaningful impressions, grouping opportunities by page, proposing a multi-week content plan, generating an initial article, reviewing its title and metadata, publishing an approved draft, requesting indexing, and preparing a 30-day measurement checklist.

Limitations and notes

The repository does not contain the hosted server implementation or credentials. Website ownership and subscription limits are enforced by the SEOPro AI backend. Search results and recommendations depend on the connected website and available Search Console data.

OAuth and API-key access can be revoked. Operational analytics record metadata such as tool name, success, latency band, authentication method, and normalized client family, but not credentials, tool arguments, article content, website content, or returned customer data. Documentation and repository assets use the MIT license, while the hosted service and its implementation are proprietary and governed by SEOPro AI’s terms.