How to Connect Claude Code to WordPress

Connecting Claude Code to your WordPress site brings your content into the terminal: the coding agent can read and update posts and pages, manage media, or inspect site configuration while you work on your theme or plugin. Easy MCP AI runs the MCP server inside WordPress, and Claude Code connects to it with a single CLI command.

In this article

• Prerequisites
• Connect via OAuth (Recommended)
• Alternative: Connect with an API Token
• Verify the Connection
• What You Can Do Once Connected
• Control What Claude Code Can Access
• Video Resources
• Security

Prerequisites

• A WordPress site served over HTTPS with Easy MCP AI installed and activated (see the installation guide).
• Pretty permalinks enabled (Settings > Permalinks set to anything other than "Plain").
• Claude Code installed and signed in.

You'll need your site's MCP endpoint URL, which is always your domain followed by /wp-json/easy-mcp-ai/v1/mcp:

https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp

You can copy it from Easy MCP AI > Dashboard in your WordPress admin: click Connect an AI client, choose your client, and copy the URL shown in the Add this site step.

Connect via OAuth (Recommended)

1. In your terminal, add the server (replace the URL with your endpoint):

claude mcp add --transport http wordpress https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp

No token is needed for this step.

2. Start Claude Code and run /mcp. Select wordpress, then choose Authenticate.
3. Your browser opens the WordPress authorization page. Log in if prompted, choose an access level (Read-only, Full access or Custom), and approve the request. Claude Code stores the credentials automatically.

See Managing OAuth Access in Easy MCP AI for access levels, grant management, and what to do after changing your site address.

Alternative: Connect with an API Token

For scripted or headless environments where the OAuth browser flow is impractical, use a token instead:

1. Create an API token in Easy MCP AI > Connections (API tokens tab) and copy it.
2. Add the server with the token as a header:

claude mcp add --transport http wordpress https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp --header "Authorization: Bearer YOUR_API_TOKEN"

You can also commit a tokenless variant for your team in the project's .mcp.json:

{
  "mcpServers": {
    "wordpress": {
      "type": "http",
      "url": "https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Never commit a real token; keep it in an environment reference or per-developer config.

Verify the Connection

Back on the Easy MCP AI Dashboard, the top of the page shows Connected: 1 OAuth grant (a higher number if you already had other connections). Once your AI client calls a tool, the call appears under Recent activity in the Dashboard sidebar.

Run /mcp again. The wordpress server shows as connected with its tool count.

Then ask something that touches your site:

Which are the five most recent posts on my WordPress site, and which of them are still drafts?

Claude Code asks for approval the first time it runs a WordPress tool.

What You Can Do Once Connected

Easy MCP AI exposes your site's capabilities as MCP tools, organized by area: posts, pages, media, comments, categories and tags, menus, custom post types, blocks, revisions, users, plugins, themes, site settings, and search. Integrations such as WooCommerce and SEO data sources are included when available. In the terminal, that pairs naturally with development work:

Create a draft page called "Pricing" using the block markup from the template file in this repo.

List the active plugins on my site and flag any that are outdated compared to wordpress.org.

Pull the content of the "About" page so I can refactor it into the new layout.

Control What Claude Code Can Access

The connection acts as the WordPress user who approved it (or the token's assigned user), so WordPress roles apply as usual. For CI or shared environments, use a dedicated token limited to the tools the job needs. Site-wide guardrails (globally disabled tools, rate limits, forced drafts, audit log) apply on top. See Creating and Managing API Tokens for details.

Video Resources

Security

If you identify a potential security vulnerability in this plugin, please disclose it responsibly. Follow the protocols on the Themeisle Security Page.