MCP Available
Deterministic SEO inspection and planning
SEO MCP discovers routes, inspects live pages, plans internal links, and runs repeatable ranking-pipeline checks.
Best for
Content teams, agencies, and founders running repeatable SEO work.
Access and usage
Available through the hosted catalog. Calls count against the shared allowance on the account plan.
Compare usage plans
Why it exists
Discover routes, inspect live pages, plan internal links, and run ranking-pipeline checks.
Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.
Connection and contract
Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.
The product-specific schema defines the inputs and outputs used by clients and downstream automation.
Current limits
Create the audit first using an authorized site binding and collected site evidence. This planning call does not collect that evidence or publish changes.
Requires an authenticated, entitled account and a completed audit in the same workspace and project. Replace audit_ref with the auditRef returned by seo_hosted_assess_site_v1. The sample reference is a placeholder.
What you get
- Discover and inspect public routes
- Plan internal links from discovered routes and page content
- Run repeatable ranking checks
Core use case
Discover routes, inspect live pages, plan internal links, and run ranking-pipeline checks.
Outcomes
- Replace generic advice with page-specific observations
- Prioritize route and internal-link fixes
- Repeat the same ranking checks after changes
Primary workflows
Route discovery Live inspection Internal-link planning Ranking checks