MainWP MCP Server

A MainWP Labs project, powered by MainWP

MainWP MCP Server is for conversational AI management inside Claude, Cursor, or any MCP-compatible client.

Looking for the MainWP Control CLI instead? MainWP Control is a CLI for managing your MainWP Dashboard from the terminal. List sites, push updates, sync data, run batch operations across dozens of sites. MainWP Control is for automation: AI automation, cron jobs, CI/CD pipelines, monitoring scripts, and batch operations. Both talk to the same Abilities API with the same safety model.

Beta Release — This project is under active development. APIs may change between versions.

An MCP (Model Context Protocol) server that connects AI assistants to your MainWP Dashboard. This lets Cursor, Claude, OpenAI Codex, VS Code Copilot, and other AI tools manage your WordPress network through natural conversation.

What You Can Do

• Site Management: List sites, check connection status, sync data, add or remove child sites
• Update Management: See pending updates across all sites, apply core/plugin/theme updates
• Plugin and Theme Control: View installed plugins and themes, activate or deactivate them
• Client Organization: Manage client records, assign sites to clients, track costs
• Bulk Operations: Sync, reconnect, or check connectivity across dozens of sites at once

Built for WordPress agencies and site managers who want AI assistance with their MainWP workflows.

Quick Start

Requirements: Node.js >=20.19.0 and MainWP Dashboard 6.0+

Option A: Run with npx (recommended)

No installation needed. Run the server directly:

npx -y @mainwp/mcp

Credentials are loaded from a settings.json file in either the current working directory or ~/.config/mainwp-mcp/settings.json. See Credential Configuration for the file format.

Option B: Clone and build (for development)

git clone https://github.com/mainwp/mainwp-mcp.git
cd mainwp-mcp
npm ci
npm run build

Then:

1. Create an Application Password (see instructions below)

2. Configure your AI tool (see Installation)

3. Start chatting: "What sites need updates?" or "Sync all my sites"

Need inspiration? See the Example Prompts for more ideas.

Credential Configuration

There are two ways to provide your MainWP credentials. Both store credentials in config files, so choose based on your workflow preference.

Option A: Per-Tool Configuration (Recommended)

Include credentials directly in each AI tool's MCP configuration using the env block. This is the standard approach you'll see in MCP server documentation.

{
  "mcpServers": {
    "mainwp": {
      "command": "npx",
      "args": ["-y", "@mainwp/mcp"],
      "env": {
        "MAINWP_URL": "https://your-dashboard.com",
        "MAINWP_USER": "admin",
        "MAINWP_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}

This is the standard approach. Each tool has its own self-contained config, and you can create a separate Application Password for each AI tool for better security.

Option B: Centralized Settings File

Store your credentials once in ~/.config/mainwp-mcp/settings.json:

{
  "dashboardUrl": "https://your-dashboard.com

... [View full README on GitHub](https://github.com/mainwp/mainwp-mcp#readme)