Publish to WordPress from Claude: research, draft, then a WordPress.com draft

Yes, through the WordPress.com connector, with limits. The Agent Index lists 16 tool names for it, mostly reads and searches, and classifies only one as a write. WordPress.com's own tools reference is more specific: its content authoring tool lists posts.create, which makes a draft by default, posts.update, block-level post-sections operations, pages.create, media.create and categories and tags.

Which of those Claude can use depends on your account. The vendor says the tools a user sees depend on the site's plan and hosting, the user's permissions and the tool settings on the account, and that choosing Read only at sign-in turns off every write tool. If Claude reports it cannot create a post, check that setting before anything else.

Early viewers asked about this. On WordPress.com's official Claude video, which has 122,000+ views, a WordPress site owner on YouTube asked in April whether they could edit their site content yet, and another asked in March when the edit function would roll out.

WordPress.com requires confirmation on every write: the agent must describe what it plans to do, ask for explicit approval and pass user_confirmed as true. posts.create makes a draft unless you say otherwise, while posts.update with a status of publish goes live immediately. A draft keeps you in the loop for the one step that is visible to readers and to Google.

The ranking tutorials take the same position. Anicca's guide pushes the post to WordPress as a draft for final review, and describes about 15 minutes of one-off setup with an application password and an environment file, plus a reusable skill. It also says the method needs Claude Code or Claude Desktop, since browser tools cannot call the REST API or read your local drive.

The WordPress.com connector skips that setup. It signs in through the browser with OAuth, so no application password sits on your laptop, and you can revoke access under Security, then Connected applications.

Start with the keyword, not the draft. Linkeddit's keyword_research_get lists your research jobs and their scored keywords with intent and a suggested landing page, and keyword_serp shows who ranks now. Ask Claude to open the top results for the keyword and write something that answers what they miss, with a source for every number.

With view brief, keyword_research_get assembles a writing brief for up to ten chosen keywords from one job. Claude writes the article, and article_save stores it in Linkeddit, so you keep a copy outside your site. On the test project the research job listed 60 scored keywords and 42 filtered out, which shows how much the first pass removes before anyone writes.

Then hand it to WordPress.com as a draft. The vendor also lists media.create, which can add an image from a public https URL up to 50 MB, and categories.list and tags.list so Claude can reuse the ones you already have.

This connector is WordPress.com's. Its documentation says Jetpack-connected self-hosted sites reach the same server and the same tool catalog, and does not describe a route for a self-hosted site with no Jetpack connection. A commenter on the official video asked whether it works on self-hosted WordPress and the question had 16 likes. Another reported a permissions error that mentioned a Jetpack plan, while the vendor page says no Jetpack plan is needed, so confirm what your account shows.

If write tools are off or unavailable, use the handoff path. Claude still writes the post and saves it with article_save. It then gives you the title, the HTML or block text and the suggested slug, and you paste it into the editor as a new draft. Nothing in this workflow requires Claude to publish.

The alternatives are the REST API with an application password, which daext describes as needing no plugin and no MCP server, or a plugin such as WP MCP Ultimate, which claude-blog.md describes as giving Claude Code 58 WordPress abilities. Those suit self-hosted sites with no Jetpack connection.