Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect WordPress to Claude Code

Let Claude draft, edit, and publish posts and pages in WordPress. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect WordPress to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect WordPress, you add a WordPress MCP server: a small hosted service that exposes WordPress's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own WordPress account. No API keys pasted into config files.

claude mcp add --transport http wordpress https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in WordPress once connected?

Full read-write WordPress access lets Claude draft a post, set the title, body, excerpt, categories, and tags, attach a featured image, and leave it as a draft for your review before publishing. It can update existing pages, manage taxonomy, and moderate comments, so content work happens where your site already lives.

  • Draft a new post with title, body, excerpt, categories, and tags, left in draft for review
  • Update an existing page or post, preserving its slug and revision history
  • Create or assign categories and tags to organize content
  • Upload an image to the media library and set it as a featured image
  • Approve, reject, or reply to pending comments after you review them
  • Publish or schedule a prepared post once you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same WordPress access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the WordPress API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when WordPress changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build WordPress connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same WordPress connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own WordPress account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on WordPress's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to WordPress?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the WordPress account it signs in with. Revoking access is one click in WordPress.

More on the WordPress connector

WordPress connector for claude.aiWebflow + Claude CodeShopify + Claude CodeSquarespace + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us