First connection

Connect your AI client to WordPress through MCPWP.

This is the shortest path from install to proof: create a scoped key, paste the endpoint into an MCP client, inspect live tools, then run one safe WordPress operation.

Before you start

Three things you need.

WordPress admin access

You need permission to install MCPWP and create API keys in the WordPress dashboard.

An MCP-capable client

Use Claude Code, Claude Desktop, Cursor, Windsurf, Codex tooling, or another client that can connect to remote MCP servers.

A scoped key

Start with read access for inspection. Add write access only when you are ready to let the assistant make changes.

Setup path

From plugin install to first MCP response.

01

Install and activate MCPWP

Install the plugin on the WordPress site you want your AI client to operate.

WP Admin → Plugins → Add New → Upload Plugin → Activate
02

Create a scoped API key

Create a key in MCPWP settings. Use read-only for discovery, then add write/admin scopes only for workflows that need them.

WP Admin → MCPWP → API Keys → New key
03

Copy your MCP endpoint

Your endpoint follows the same pattern on every site. The key decides what the client can do.

https://your-site.com/wp-json/mcpwp/v1/mcp
04

Ask the client to inspect the site

The first successful connection should be read-only: confirm site info and available tools before making changes.

Inspect this WordPress site and list the MCPWP tools available to my key.
Client config

Use the same endpoint and key in your MCP client.

Keep the server name simple and product-aligned. Do not paste admin keys into clients that only need read access.

{
  "mcpServers": {
    "mcpwp": {
      "url": "https://your-site.com/wp-json/mcpwp/v1/mcp",
      "headers": {
        "X-API-Key": "mcpwp_your_scoped_key"
      }
    }
  }
}
Safety checklist

Make the first run boring on purpose.

Start read-onlyVerify site info and tools before granting mutation scopes.
Name the key clearlyUse labels like Claude Code Read or Agency Builder Write.
Check tool categoriesDisable categories the client does not need.
Review activity logsConfirm every request is visible and attributable.
Proof command

Your first success is a site inspection.

Once the client responds with your site name, WordPress version, active integrations, and available MCPWP tools, the conversion path has worked.