WP Engine MCP Server

What is WP Engine MCP Server?

A TypeScript implementation of an MCP server for the WP Engine API, providing tools and resources for interacting with WP Engine accounts, sites, installs, and backups. It supports both local (stdio) and remote (HTTP) transports.

How to use WP Engine MCP Server?

Install dependencies with npm install, build with npm run build, then set environment variables WP_ENGINE_API_USERNAME and WP_ENGINE_API_PASSWORD. Run locally with npm run start:stdio or remotely with npm run start. For HTTP transport, use the --port and --auth-token command line options.

Key features of WP Engine MCP Server

• Get account, site, install, and backup information
• Create and manage sites, installs, and backups
• Domain management (add, update, delete domains)
• Cache purging (object, page, cdn, or all)
• SSH key management (get, create, delete)
• Local (stdio) and remote (HTTP) transport support

Use cases of WP Engine MCP Server

• Automatically create WordPress installs and configure domains
• Manage backups and trigger cache purges in CI/CD pipelines
• Retrieve account and site details for monitoring
• Manage SSH keys programmatically
• Integrate WP Engine management into AI assistant workflows via MCP

FAQ from WP Engine MCP Server

What authentication is required?

The server requires WP Engine API credentials set as environment variables WP_ENGINE_API_USERNAME and WP_ENGINE_API_PASSWORD. For HTTP transport, a bearer token (default: wpengine-mcp-token) is used for authentication.

What transports are supported?

The server supports both local (stdio) transport for use with local MCP clients