SpyFu MCP Server vs SEOmatic MCP
What the SpyFu MCP does, what it costs, and when SEOmatic's MCP server is the better fit: your own Search Console data, fixes staged in your CMS for your approval, and a verdict on whether each change worked.
- Your own Search Console data, free
- Fixes staged in 18 CMSs, with your approval
- Each change measured afterwards
Last Checked
October 2026
Endpoint
https://app.seomatic.ai/api/mcp
Full Docs
Every tool, parameter and cost: SEOmatic MCP docs.
SEOmatic MCP and SpyFu MCP, Compared
The Short Answer
SpyFu does not publish an official MCP server as of October 2026. A community server wraps the SpyFu API so an AI agent can read SpyFu's paid and organic competitor data; it does not change your website. SEOmatic's MCP server (https://app.seomatic.ai/api/mcp) is built for a different job. It reads your own Google Search Console data for free, audits your site, and can stage the fix in your CMS (18 platforms), wait for your approval, then measure whether the change worked. Pick the SpyFu MCP when you research competitors' paid search and want SpyFu's ad history in your agent. Pick SEOmatic when you want your own Search Console numbers for free and an agent that ships the fix in your CMS.
What the SpyFu MCP Does
| SpyFu MCP | |
|---|---|
| Official | No, community-built |
| Runs where | Your machine (Python 3.11+), community-built |
| Sign-in | Your own SpyFu API key |
| Price / plan needed | A SpyFu plan with API access |
| Data | Paid and organic competitor data: ad history, keywords, rankings |
| Changes your site | No |
Because it is community-built, review its code before connecting it, and expect setup on your own machine.
Sources, checked October 2026: spyfu-mcp-server on GitHub.
SEOmatic MCP vs SpyFu MCP
| SEOmatic MCP | SpyFu MCP | |
|---|---|---|
| Runs where | Hosted | Your machine (Python 3.11+), community-built |
| Sign-in | OAuth 2.1 with PKCE, or an API key | Your own SpyFu API key |
| Your own Search Console data | Yes, free with no limit | No |
| Data | Search Console, GA4, site audits, keyword volumes, SERPs, backlinks | Paid and organic competitor data: ad history, keywords, rankings |
| Changes your site | Yes, staged in 18 CMSs, live after your approval | No |
| Rollback | Yes, with a check for edits made since | No |
| Measures whether a change worked | Yes: verified, ineffective or regressed | No |
| Price / plan needed | Free plan: Search Console, audits and page checks unlimited | A SpyFu plan with API access |
When to Use Each
Pick the SpyFu MCP when you research competitors' paid search and want SpyFu's ad history in your agent.
Pick SEOmatic when you want your own Search Console numbers for free and an agent that ships the fix in your CMS.
Or use both. MCP servers sit side by side in the same agent. Ask SpyFu for its data, then ask SEOmatic to check your own Search Console and stage the fix.
Try SEOmatic Next to SpyFu
Add the URL below as a remote MCP server in your agent and sign in; SpyFu can stay connected beside it. Reading your Search Console, audits and page checks are free with no limit, and staged fixes are part of paid plans. How approval, rollback and the verdict on each change work is on the SEO MCP server page.
https://app.seomatic.ai/api/mcpMore SEOmatic MCP Pages
Frequently Asked Questions
Can the SpyFu MCP change my website?
No. It reads SpyFu data; it does not change your website. SEOmatic can stage changes in WordPress, Shopify, Webflow and 15 more platforms, and by default nothing goes live until you approve it.
What is the difference between the SpyFu MCP and SEOmatic's MCP?
The SpyFu MCP gives your agent SpyFu's data. SEOmatic gives it your own Search Console data for free, then stages fixes in your CMS for your approval and measures whether each change worked.