01 · Records and state owned
Read and manage posts, pages, comments, tags, categories, media and related site/account content; per-tool read/write toggles with read-only tools enabled by default
Automattic
WordPress.com
Curated anchor platform in web publishing and cms with material relevance to the Marcom operating stack and a first-party developer surface.
Content, CMS, creative & DAMSystem of productionBYO-UI-ready platform
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
Read and manage posts, pages, comments, tags, categories, media and related site/account content; per-tool read/write toggles with read-only tools enabled by default
03 · Actions and write paths
No WordPress.com MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.
04 · Authentication and permissions
WordPress.com uses OAuth 2.1 and user approval for tool calls. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.
05 · Monitoring, approval, and recovery
WordPress.com uses OAuth 2.1 and user approval for tool calls. Full write capabilities arrived in 2026. WordPress.com uses OAuth 2.1 and user approval for tool calls. Full write capabilities arrived in 2026. Distinguish the managed WordPress.com server from the separate WordPress/mcp-adapter for self-hosted sites and local Studio server.
06 · Gaps and implementation limits
WordPress.com uses OAuth 2.1 and user approval for tool calls. Full write capabilities arrived in 2026. Distinguish the managed WordPress.com server from the separate WordPress/mcp-adapter for self-hosted sites and local Studio server.
Agent access
MCP and adjacent posture
Verified first-party provider MCPBuilt-in WordPress.com hosted MCP; separate official self-hosted WordPress MCP Adapter and Studio MCPCurrent service on paid WordPress.com plans
Role: provider
Read scope: Read and manage posts, pages, comments, tags, categories, media and related site/account content; per-tool read/write toggles with read-only tools enabled by default
Write scope: No MCP writes verified; the documented surface is read-only.
Authentication: WordPress.com uses OAuth 2.1 and user approval for tool calls.
Approval boundary: WordPress.com uses OAuth 2.1 and user approval for tool calls. Full write capabilities arrived in 2026.
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 access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability4
Observability3
Documentation5
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Automattic ships these experiences.
Single-platform patterns
- Editorial, publishing, and site-management studio
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- WordPress.com + CRM or campaign platform: campaign asset assembly room
- WordPress.com + work-management system + analytics or distribution platform: 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.
5 recorded sources
MCPRepresentative source
https://developer.wordpress.com/docs/mcp/ ↗WordPress.com uses OAuth 2.1 and user approval for tool calls. Full write capabilities arrived in 2026. Distinguish the managed WordPress.com server from the separate WordPress/mcp-adapter for self-hosted sites and…
- Publisher updated
- Jun 19, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developer.wordpress.com/docs/api/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Oct 7, 2025
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developer.wordpress.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.
Webhooks / extensionsSource inventory
https://developer.wordpress.com/docs/api/webhooks/ ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Jul 11, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://wordpress.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.
Verified fact
Tied to the representative first-party source or targeted access review.
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.