WordPress.com Agent and MCP write: when .com is enough vs when you need a developer

The WordPress Agent update of 15 October 2026, together with MCP write for external agents (available since March, announcement page updated on 16 October), shortens the path from brief to draft on paid WordPress.com. The agency still owns architecture, plugin whitelist, multilingual SEO, and the publish gate. An offer that says “the Agent will ship the whole production site” fails on the first ERP ticket or security incident. An offer that ignores Agent and MCP write loses the kickoff on time-to-first-look.

For nearshore and client-facing engineering the useful split is: what landed in Automattic’s product, how it changes the brief and the quote, and where the Abilities API on your own host begins.

If you are building or migrating a site and are unsure whether to stay on WordPress.com Agent or move to self-hosted with MCP integration, send a short brief via contact: hosting, WooCommerce yes/no, number of locales, compliance requirements. The reply is a path recommendation, not a generic “we use AI”.

#What’s new in WordPress.com Agent (October 2026)

Ronnie Burt’s official post (“Build Faster, Edit Your Way: What’s New with WordPress Agent”, 15 October 2026) describes one package. Below: project decisions that follow from that package.

#How long site generation takes in WordPress.com Agent

Most sites are ready in under four minutes, and generation takes less than half the time it used to. For the client that is a shorter feedback loop at kickoff. For the agency: less waiting for a “first look”, more time for information architecture, structured data, and SEO decisions.

Practical quoting consequence: the “mockup / first variant” line loses hourly weight. The lines for keyword discovery, content map, plugin rules, and acceptance criteria gain weight. If you still sell three days of “first UI draft” without a reason, the client will compare you to the Agent and you will look expensive.

#Does WordPress.com Agent build a custom theme

The Agent builds a theme from goals and answers instead of handing over a library starter. It is still a generated theme. Check the output for:

• typography and spacing consistency across breakpoints,
• contrast and focus states (especially on CTAs),
• image performance (formats, sizes, lazy load),
• a sensible content model (do H1-H3 match intent, or are they decoration only).

A generated theme is a sketch. Brand book, design tokens, or a Figma library stay the visual source of truth; the Agent speeds the first variant toward that truth.

#AI Editor and Annotate mode in WordPress.com Agent

Under Appearance there is a simpler AI Editor with Preview and Edit tabs. Annotate mode lets you mark sections, stack edits, and send them to the agent in one shot. On a client call it works like a shared board: click, comment, send, instead of rewriting prompts into Notion.

For agency process design:

1. Discovery call: client states goals.
2. Agent generates the first variant.
3. Annotate live: 5-12 notes in one batch.
4. Second round only after Guidelines are saved (more below).

Without step 4 you return to prompt chaos. Annotate without Guidelines is fast cosmetic cleanup that disappears in the next session.

#Plugin installation through WordPress.com Agent

The Agent can recommend, install, activate, and update plugins in the conversation. This is the strongest risk point in the whole package. Every installed plugin is attack surface, theme conflict risk, and potential maintenance cost.

At kickoff agree a whitelist before you open chat the first time:

• allowed: specific SEO, forms, cache (if needed at all on .com),
• banned: “full SEO suites”, unknown page builders, random security scanners from the catalogue,
• procedure: Agent proposes, human approves, only then install.

Without a whitelist the Agent “adds tools” in an hour and leaves you a quarter of technical debt.

#Guidelines in WordPress.com Agent (settings)

Site purpose, audience, tone, and image style live under Settings > Guidelines. Later chats remember the context. In practice this is a living brand brief inside the product, not a PDF in Drive.

Treat Guidelines as a deliverable:

• after discovery: first version written with the brand owner,
• after every voice change: update Guidelines before the next Agent session,
• review once per content sprint: do Guidelines still describe the product you sell.

Agencies that keep the brief only in Notion and start the Agent “from zero” waste exactly this feature.

#WordPress.com Agent in Slack

After connecting in account settings you can message the Agent from Slack. Useful for content ops. Risky if the channel has no clear ownership: who approves drafts, who has .com account access, who sees the MCP activity log.

Minimum model: a private channel or DM with the Agent, 2FA on the WordPress.com account, and a named list of people with publish rights outside the Agent.

Availability: the Agent can be enabled on any paid WordPress.com plan. Sites built with it get the AI Editor by default; an existing site needs a block theme to use the AI Editor.

#WordPress.com MCP write: 19 write tools

The official announcement by Jonathan Bossenger on the WordPress.com blog (20 March 2026, page updated 16 October 2026) lists:

• 19 write abilities across six content types: posts, pages, comments, categories, tags, media,
• before writing, the agent reads the theme’s colours, fonts, spacing, and block patterns,
• new posts default to drafts; editing a published post shows a warning that the change goes live immediately,
• the agent describes each planned change and waits for explicit confirmation,
• deleted posts, pages, comments, and media go to the trash for 30 days; deleting categories and tags is permanent and needs extra confirmation,
• all changes visible in the Activity Log,
• available on all paid plans, switched on per operation at wordpress.com/me/mcp.

External agents (Claude, ChatGPT, Cursor, OpenClaw and similar) can write to a .com site. Self-hosted reaches the same direction through the MCP Adapter and Abilities API. On .com you control Automattic’s product; on your own host you control the abilities registry, permission_callback, and infrastructure. A public read-only edge example is our MCP live server guide.

#Does MCP write publish live immediately

Draft + log + reversible delete reduce accidental publish risk. They do not reduce:

• YMYL content written without fact-check,
• mass thin pages for SEO,
• media uploaded without licences,
• comments moderated by an agent without a policy.

The publish gate stays human. MCP write wired to Cursor on an account with publish rights bypasses that gate: that is a process failure you close with roles and 2FA.

#WordPress.com Agent vs self-hosted WordPress

Wider agent and block context: agentic WordPress MCP block runner. Product-side MCP integrations: MCP AI integration.

#When WordPress.com Agent is enough for a client

#Landing and company blog on WordPress.com Agent

The Agent is enough for the first site version and ongoing content ops via Guidelines + Annotate. The agency sells: local SEO discovery, LocalBusiness schema, GSC, Guidelines maintenance, review of MCP drafts. It does not sell “custom theme from scratch in 6 weeks” if the Agent covers 80% of the UI.

#WooCommerce with warehouse: Agent or developer

The Agent can speed the landing and product copy. Checkout, stock, tax, and ERP stay outside the Agent. Self-hosted (or VIP / enterprise host) with custom abilities and tests. MCP write on .com does not solve HPOS or the Store API.

#Multilingual WordPress for AI Mode and AEO

Agent and MCP write generate drafts. Hreflang, content depth, llmCard, citable facts in the first 80 words, and CTR vs position in GSC are editorial-engineering work. The AI Mode and AI Overviews link changes reported on 15 October (Search Engine Roundtable) come without click data for site owners; citability still beats a prettier carousel.

#How to price a project with WordPress.com Agent

1. Shorter kickoff on mockup, not on discovery. Sub-4-minute generation + Annotate means the client sees a variant before you finish discovery. Do not shorten SEO and data discovery. Shorten waiting for the mockup.
2. Guidelines = deliverable. Hand the client an editable brief in Settings, not only a PDF. That reduces drift across content sprints.
3. Plugin policy before chat. At kickoff: allowed plugin list. An Agent without a whitelist generates debt in an hour.
4. MCP write ≠ publish. Draft + human approval stays in the process. For YMYL and stores: staging or a review queue, even if the tool can write from Cursor.
5. Nearshore still sells review. The Agent speeds work; it does not sign the SLA. Hiring for AI efficiency plus real code review: WordPress + AI hiring.

#Security for WordPress.com Agent and MCP write

• 2FA on every account with Agent and MCP dashboard access.
• Separate roles: who may connect MCP, who may publish.
• MCP activity log: weekly review when content ops is active.
• No MCP write on a live store without a staging mirror.
• Slack: only people under contract and NDA; no shared workspace guests with Agent rights.
• Backup / export before bulk MCP operations (even with reversible deletes).

#SD AI agent 1.25 vs WordPress.com Agent

On 15 October 2026 the SD AI Agent plugin on WordPress.org shipped 1.25.0: approved remote MCP servers, OAuth, scoped tool discovery, confirmations before invoke. That is a self-hosted ecosystem signal: remote MCP with control, not “connect anything”.

Do not confuse SD AI Agent with WordPress.com Agent. Different product, same risk class (tools with write permissions). If you run self-hosted for UK, EU, and DACH clients, 1.25.0 is a vendor due-diligence checklist: OAuth, scope, confirmations. If someone offers “full database access over MCP without confirmations”, you refuse.

#What to promise a client with WordPress Agent

Sell

• faster UI kickoff on WordPress.com,
• living Guidelines as a deliverable,
• content ops with MCP write + a human publish gate,
• migration from a .com prototype to self-hosted when complexity grows,
• audit of plugin whitelist and MCP logs.

Do not promise

• that the Agent replaces WooCommerce B2B,
• that MCP write “handles SEO” without editorial work and measurement,
• that React / Gutenberg / edge somehow “comes out of chat”,
• a fixed fee for “unlimited Agent sessions” without a scope limit.

#WordPress.com Agent rollout checklist for agencies

• Client on paid WordPress.com: enable Agent, fill Guidelines with the brand owner
• Agree plugin whitelist before the first chat session
• Test Annotate on one page (stack 3-5 notes, one batch)
• Connect MCP write only on a 2FA account; drafts, not publish
• Self-hosted: map the same operations to abilities + MCP Adapter; do not copy the .com flow 1:1
• Measure time: brief to first draft (with Agent) vs brief to first review (without) - keep both numbers in the quote
• Write into the proposal: what the Agent does, what the engineer does, who publishes

#How to measure WordPress.com Agent and MCP write impact

Without numbers the opening claim stays an opinion. On the first .com project with the Agent collect four metrics:

1. Time from signed brief to first UI variant (minutes or hours). Compare to the last similar project without the Agent.
2. Annotate rounds to layout acceptance (target: 2-3 batches, not 15 single prompts).
3. Plugins installed by the Agent vs whitelist (target: zero outside the list).
4. Time from MCP draft to publish (target: a fixed review queue, not “live immediately”).

If (1) halves while (3) and (4) grow without control, you spend the kickoff gain on incidents. The monthly client report should show these four numbers, not a screenshot of the Agent chat.

#MCP write, REST API and Abilities API - differences

On a call with the client’s CTO three names collapse into one. Separate them:

• WordPress REST API - classic HTTP transport. It still exists. Agents can use it, but without a shared registry of “what is allowed” each agent invents its own endpoints.
• Abilities API (core from 6.9) - a registry of operations with schema, permissions, and callback. This is the language WordPress uses to describe “what the system can do”. Details: Abilities API.
• MCP - the protocol external agents use to discover tools. On self-hosted the bridge is MCP Adapter. On WordPress.com, MCP write is the product exposure of write (19 tools) with drafts and a log.

For agencies: teach the client that “we have MCP” without abilities and without a publish gate only means someone plugged in a write-capable tool. That is not architecture.

#Annotate in WordPress.com Agent on a client call

Without a protocol Annotate becomes “one more tweak” chaos. A proven 45-minute call flow:

1. Minutes 0-5: open Preview, confirm Guidelines out loud (purpose, audience, tone). If Guidelines are stale, fix them first, then touch UI.
2. Minutes 5-25: client speaks, you mark in Annotate. Do not debate every font separately. Build the stack.
3. Minutes 25-30: send the batch to the Agent, wait for the result.
4. Minutes 30-40: second round only on blockers (CTA, navigation, hero). Everything else goes to the backlog.
5. Minutes 40-45: record decisions: what entered Guidelines, what is an engineering ticket outside the Agent.

After the call send a short summary: batch change list, list of items outside the Agent (integrations, SEO, compliance). That document protects you from “but on the call we said the Agent would do the warehouse”.

#WordPress.com Agent on the PL nearshore market

English-speaking B2B clients often start on cheap hosting or on WordPress.com “because marketing promised AI”, then ask for warehouse sync, local payment rails, or multilingual EN/DE/PL with separate GSC properties. The Agent closes the first company site well. It closes poorly once invoicing, stock levels, and two locales with separate Search Console enter the room.

In a nearshore quote:

• phase 0 (Agent / .com): fixed discovery + Guidelines + 2 Annotate rounds,
• phase 1 (self-hosted or VIP): migration when an integration or compliance requirement appears,
• exit criteria from phase 0: a trigger list (ERP, SSO, >N SKUs, log requirements beyond .com).

Without exit criteria the client stays on .com with the Agent longer than they should, and you inherit the ticket “why doesn’t checkout talk to the warehouse”.

#What WordPress.com Agent will not solve

WordPress.com Agent does not speed up:

• migrating legacy PHP without tests,
• fixing Core Web Vitals after a bad generated theme (sometimes it worsens LCP if the Agent drops a heavy hero without control),
• legal disputes and ecosystem governance (a separate topic, outside this piece),
• Google indexing (still GSC, IndexNow, content; the 16 October Indexing API docs change removed old quota wording, it did not add a magic button).

If the client arrives with “zero clicks at position 2 on the pricing page”, read AI Overviews and AI Mode first. Do not install the Agent as a SERP remedy.

WordPress Day for AI in Faro (24 October 2026) gives a full community day to the practical impact of AI on WordPress, with a business track and a developer track. The claim of this piece is narrower: the easy gain is 4 minutes to draft. The hard gain is publish gate, whitelist, and ownership.

#Offer split: Agent, MCP write, custom development

A structure you can paste into a proposal (individual pricing, as always outside the pricing page):

The client sees where the Agent ends. You protect yourself from scope creep (“since you have AI, drop ERP into the same sprint”).

#When to send a delivery inquiry (not only “click through the Agent”)

Write when at least one of these is true:

• store, ERP, warehouse, Subiekt, Baselinker, or payments outside the .com default,
• more than one language with separate SEO / AI Mode,
• a requirement for logs, SSO, or audit trail outside the WordPress.com panel,
• Agent or MCP write already runs, and the plugin whitelist and publish gate do not,
• you need a WordPress developer for ownership, not for another prompt.

Four points in the email are enough: URL or hosting plan, business goal in one sentence, deadline, constraints (GDPR, YMYL sector, budget as individual ranges after scope). The more concrete the brief, the faster the quote and the less drift in discovery.

#WordPress.com Agent for draft, developer for ownership

October 2026 shortens the distance from conversation to draft on WordPress.com and exposes write via MCP to external agents, with drafts and a log. Custom WordPress stays where stores, integrations, and SEO under the next AI Mode UI change live: Abilities API, your own MCP, and code review.

“.com Agent vs self-hosted” audit or delivery quote: contact. Related services: MCP AI integration, WordPress developer.