SEO Data Services Subsystem
How More MCP coordinates with external data providers like Google Search Console and DataForSEO via the SEODataManager.
What is the SEO Data Services Subsystem?
Beyond WordPress core manipulation, modern marketing workflows require real-time search performance and keyword metrics. More MCP includes an optional SEODataManager subsystem designed to bridge third-party analytical APIs into your AI agent’s toolbelt.
Architecture
The SEO services architecture operates alongside the standard Capabilities registry:
- Core WordPress tools run locally via standard hooks and
$wpdb. - SEO Data providers run through
SEODataManager(includes/Services/). - When credentials are provided in More MCP -> Settings -> Services, additional specialized tools become active.
Supported Provider Families
| Provider Prefix | Service Description | Configuration Requirements |
|---|---|---|
gsc_* |
Google Search Console metrics (clicks, impressions, queries) | Service Account JSON or OAuth token |
ga4_* |
Google Analytics 4 traffic and conversion analytics | GA4 Property ID and API credentials |
dataforseo_* |
Live SERP rankings, search volume, and backlink data | DataForSEO API login and password |
semrush_* |
Competitor domain analysis and organic rankings | SEMrush API key |
seranking_* |
Keyword position tracking and audits | SE Ranking API key |
ahrefs_* |
Domain rating and backlink profile inspection | Ahrefs API token |
How Tools Are Dispatched
Unlike core WordPress tools that are always loaded in memory:
SEODataManagerinspects which external services have valid API credentials stored in WordPress options.- If Google Search Console is connected, tools like
gsc_get_search_analyticsandgsc_inspect_urlare injected dynamically into the MCP tool catalog. - If no external credentials are configured, the MCP server stays minimal and lightweight, exposing only the 107 baseline WordPress tools.
Caching & Rate Limiting
To prevent running out of API credits or triggering rate limits:
- API responses from external providers are cached locally in WordPress transients.
- Cached queries return instantly to AI agents without incurring third-party API costs.
- Cache duration can be adjusted under More MCP -> Settings -> Services.