Wordpress MCP Server

Wordpress MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Wordpress MCP directly instead of describing what you should do. MCP server for WordPress automation and management using browser automation and API integration.

What you get

A comprehensive MCP server for WordPress automation. TanukiMCP provides powerful AI-driven tools for creating, managing, and customizing WordPress websites through the Model Context Protocol (MCP), compatible with Cursor, Claude, and other MCP-enabled AI tools.

TanukiMCP is a cloud-based automation platform that enables users to perform complex WordPress tasks through a dedicated web application. It leverages the Model Context Protocol (MCP) and integrates directly with the WordPress REST API to provide a seamless automation experience.

• WordPress site management tools
• Strategic planning and design tools
• Wireframing and design document creation
• Site architecture planning and visualization
• Page creation and content management
• Theme customization and management

What the assistant can call

Once Wordpress MCP is connected, these are the calls the assistant has available:

• GPT — 4.1** (Default): The most capable model for complex WordPress tasks and coding
• advanced — Uses the GPT-4.1 model
• basic — Uses the GPT-4.1-mini model
• Configuration — 1. Install and activate the TanukiMCP Dashboard Plugin in your WordPress site 2. Navigate to the TanukiMCP settings page in your WordPress admin 3
• Authentication — All requests from the dashboard plugin must include: - Authorization: Bearer 3c9a406341969edf38b3d6d0c8f7685c header - Content-Type: application/json

Configuration and credentials

You will need 3 environment variables: TANUKIMCP_MASTER_KEY, REQUIRE_API_KEY, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wordpress MCP's toolset — GPT, advanced, basic and 2 more — is a fair guide to whether it matches your workflow. It is maintained by AppleJax2; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wordpress mcp mcp server does with a few real requests.