Server Wp MCP Server

The WordPress MCP server enables AI assistants to interact with WordPress sites through a standardized interface. It handles authentication and provides a secure way to discover and interact with WordPress REST API endpoints. The server wp mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server that enables AI assistants to interact with WordPress sites through the WordPress REST API. Supports multiple WordPress sites with secure authentication, enabling content management, post operations, and site configuration through natural language.

• Multi-Site Support — Connect to multiple WordPress sites simultaneously
• REST API Integration — Full access to WordPress REST API endpoints
• Secure Authentication — Uses application passwords for secure API access
• Dynamic Endpoint Discovery — Automatically maps available endpoints for each site
• Flexible Operations — Support for GET, POST, PUT, DELETE, and PATCH methods
• Error Handling — Graceful error handling with meaningful messages

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• wp_discover_endpoints — The wp_discover_endpoints tool exposed by this server
• wp_call_endpoint — The wp_call_endpoint tool exposed by this server

Configuration

You will need 3 environment variables: USER, PASS, WP_SITES_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the server wp mcp mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Server Wp MCP's toolset — wp_discover_endpoints, wp_call_endpoint — is a fair guide to whether it matches your workflow. It is maintained by emzimmer; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Server Wp MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.