Power MCP Server

The Power MCP service lets you connect AI agents (like Claude Code CLI) to your WordPress sites using the Model Context Protocol. Search abilities, run WordPress operations, and manage sites — all from natural language conversations.

Private Beta

The MCP server is in private beta. Endpoints, tools, and authentication may change before general availability. OAuth support is coming soon.

What you can do

• List your WordPress sites — see all sites registered to your WP Engine account
• Search abilities — find WordPress operations by keyword across all your sites
• Run abilities — execute WordPress actions (create posts, manage plugins, etc.) from your AI agent
• Manage content — create, update, and delete posts, pages, and media

All through natural language conversations in Claude Code CLI or any MCP client.

Quick start

1. Create a personal API key in the Power console
2. Configure Claude Code with the MCP server URL and your key
3. Connect your WordPress account to each site (one-time setup)
4. Run your first ability — create a post, manage plugins, or search content

The getting started tutorial walks through the complete setup in 10 minutes.

How it works

1. You configure Claude Code CLI with the Power MCP service URL and a personal API key in ~/.claude/settings.json
2. Claude connects to the MCP server when you start a session
3. You ask Claude to perform a WordPress operation in natural language
4. Claude calls the MCP server with the appropriate tool (list_account_sites, search_abilities, run_site_ability)
5. The gateway verifies your identity, checks permissions, and executes the ability on your WordPress site
6. Claude returns the result to you

The MCP server acts as a bridge between AI agents and your WordPress sites, translating natural language requests into WordPress API calls.

Authentication

Two authentication methods:

Method	Status	Use case	Identity
Personal API key	Available now	Human users, Claude Code CLI	Key owner’s Okta account
OAuth 2.1	Coming soon	Interactive consent, multi-account	User-selected account

Personal API keys are required for WordPress ability execution. See API keys for setup instructions.

The two connections

A site reaches Power through two separate connections.

Site connection

The site’s administrator registers it to your WP Engine account, once. You can then:

• See the site in list_account_sites
• View site metadata
• Search its knowledge base

WordPress account connection

Only needed if you want to run WordPress abilities or manage the site — from Coworker in the Power console, or from an MCP client. You connect your own WordPress user to the site, once per site, and abilities then run as that user:

• List abilities available on the site
• Execute abilities as your WordPress user
• Search abilities across connected sites

It requires explicit consent in WordPress admin, and it is per person: connecting a site grants nobody the ability to act on it. See Site and WordPress account connections for details.

Available tools

Tool	Needs	Purpose
ping	Bearer token	Health check and server version
list_account_sites	Site connection	List active sites by default, or filter by registration status
search_abilities	WordPress account connection	Find abilities by keyword
list_site_abilities	WordPress account connection	List all abilities for a site
run_site_ability	WordPress account connection	Execute a WordPress ability

All tools accept JSON-RPC 2.0 requests over Streamable HTTP.

Tool documentation coming soon

Complete tool schemas will be available in the reference section.

Example conversations

List your sites

claude "Use the coworker MCP server to list all my active WordPress sites"

Claude calls list_account_sites and returns:

You have 3 sites:
1. example.com - Connected, 42 abilities
2. staging.example.com - Needs WordPress account connection
3. dev.example.com - Connected, 38 abilities

Create a post

claude "Use the coworker MCP server to create a draft post on example.com titled 'Hello from Claude' with the content 'This was created via MCP.'"

Claude:

1. Searches for the core/create-post ability
2. Runs it with your input
3. Returns the new post ID and admin link

Search abilities

claude "Use the coworker MCP server to find WordPress abilities for managing comments"

Claude searches across your connected sites and returns matching abilities.

Documentation structure

This documentation follows the Diataxis method:

Getting started (Tutorial)

Learning-oriented guide that walks you from zero to your first ability execution in 10 minutes.

How-to guides (Task-oriented)

Practical guides for specific tasks:

• Configure Claude Code CLI
• Search for abilities
• Handle errors
• Troubleshoot connection issues

Reference (Information-oriented)

Technical specifications:

• Tool schemas and parameters
• Authentication details
• Error codes
• Data models

Concepts (Understanding-oriented)

Explanations of how things work:

• Site and WordPress account connections
• MCP server architecture
• Personal vs project API keys
• Security model

Supported MCP clients

The server works with any MCP client that supports HTTP transport:

Client	Status	Notes
Claude Code CLI	✓ Tested	Recommended; native HTTP support
MCP Inspector	✓ Tested	Great for debugging
Custom clients	✓ Supported	Use any HTTP library

Multi-client support coming soon

Configuration guides for other MCP clients will be available soon.

Endpoint

Production: https://api.ai.wpengine.com/v1/mcp

All requests use Streamable HTTP (POST-only, JSON-RPC 2.0).

Rate limits

• 100 requests/minute per account
• 50 requests/minute per API key

Exceeded limits return 429 Too Many Requests.

Support

• How-to guides — Task-oriented recipes
• Reference documentation — Technical specifications

What’s next

• Get started → Set up Claude Code CLI in 10 minutes
• How-to guides → Task-oriented recipes
• Reference → Complete API documentation
• Concepts → Understand the architecture