01 · Records and state owned
SEO and backlink reports; keyword and domain intelligence; Trends traffic and market data when subscribed; and read-only Projects API v3 project data.
Semrush
Semrush
Semrush anchors competitive SEO and traffic intelligence because its first-party MCP exposes agent-readable SEO, backlink, keyword, traffic, market, and project reporting through a hosted, metered interface.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
All documented SEO API and subscribed Trends API data, plus read-only Projects API v3 methods for retrieving project information.
03 · Actions and write paths
Semrush MCP is read-only for Projects API v3 and the reviewed MCP page documents data retrieval rather than project creation, settings changes, or other actions. Direct Semrush APIs may expose mutations, but those are outside this MCP scope.
04 · Authentication and permissions
The hosted endpoint uses OAuth by default or an account API key in the Authorization header. Available datasets and units follow the authenticated Semrush subscription; versioned API keys have their own permissions and expiration settings.
05 · Monitoring, approval, and recovery
Semrush meters MCP calls through API units and warns that AI responses can be incomplete or inaccurate. API use is also subject to request, concurrency, caching, and product-specific limits; BYO-UI should surface unit cost and source parameters before costly retrievals.
06 · Limits and caveats
MCP uses Streamable HTTP only. SEO access is plan/unit dependent, Trends requires a Trends subscription, Projects access is read-only v3, general API traffic is capped at 10 requests per second and 10 concurrent requests per account, and caching beyond one month requires written consent.
Agent access
MCP support
Official MCP serverVendor-hosted remote MCPCurrent documented service
Support: Official MCP server
Read scope: Retrieve Semrush SEO, backlink, keyword, domain, traffic, market, and authorized project-reporting data within the subscribed API products and remaining unit balance.
Write scope: No Semrush MCP write surface was documented in this review; Projects MCP access specifically excludes creation, settings changes, and other actions.
Authentication: Hosted Streamable HTTP with interactive OAuth by default; an API key in `Authorization: Apikey ...` is the documented fallback for clients without OAuth.
Approval boundary: The reviewed MCP catalog is retrieval-only, so it has no documented mutation approval flow. BYO-UI should instead require user acknowledgement before unusually expensive unit-consuming queries and should show the selected database, date range, and scope.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Semrush ships them.
Single-platform patterns
- SEO, paid-search, and market-intelligence workbench
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Semrush + warehouse or semantic layer: executive insight brief
- Semrush + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
MCPRepresentative source
https://developer.semrush.com/api/v4/introduction/semrush-mcp/ ↗MCP data families, read-only Projects boundary, OAuth/API-key authentication, Streamable HTTP, plans, and unit consumption
- Publisher updated
- Jul 15, 2026
- BYO-UI reviewed
- Jul 22, 2026
Full first-party MCP scope, authentication, transport, plan, and write-boundary review completed 2026-07-22
APISource inventory
https://developer.semrush.com/api/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developer.semrush.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.semrush.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
API limitsSource inventory
https://developer.semrush.com/api/v4/introduction/api-usage-restrictions/ ↗request, concurrency, caching, and product-specific limits
- Publisher updated
- Jul 15, 2026
- BYO-UI reviewed
- Jul 22, 2026
request, concurrency, caching, and product-specific limits reviewed from live first-party documentation on 2026-07-22.
API changelogSource inventory
https://developer.semrush.com/api/v3/introduction/release-notes/ ↗API documentation versioning, key compatibility, and Projects API release state
- Publisher updated
- Jul 15, 2026
- BYO-UI reviewed
- Jul 22, 2026
API documentation versioning, key compatibility, and Projects API release state reviewed from live first-party documentation on 2026-07-22.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.