Best MCP Servers for WordPress Developers in 2026

WordPress development has a particular kind of complexity: PHP templates, a MySQL database full of serialized options and post meta, a hook system with thousands of filters and actions, and a plugin ecosystem where conflicts are the norm. MCP servers give your assistant access to your actual WordPress site, database, theme files, and accurate documentation so it stops guessing and starts working with your real configuration.

graph LR
    A[Your Editor] --> B[AI Assistant]
    B --> C[WordPress MCP]
    B --> D[MySQL MCP]
    B --> E[Filesystem MCP]
    B --> F[GitHub MCP]
    B --> G[Context7 MCP]
    C --> H[WordPress REST API]
    D --> I[MySQL Database]
    E --> J[Theme & Plugin Files]
    F --> K[GitHub Repos]
    G --> L[WP Developer Handbook]

WordPress MCP -- Site Management from Your Editor

Author: Community | Tools: 10 | Requires: WordPress URL and app password

Ten tools covering core WordPress content operations: creating and editing posts, managing pages, uploading and organizing media, reading site settings, and interacting with custom post types. Communicates through the WordPress REST API using application passwords.

Why use it

• Create a set of test posts with realistic content, specific categories, and placeholder images for theme development
• Move 50 posts between categories and update their slugs to match a new URL structure in one step
• Manage media uploads and organization without opening the admin panel
• Interact with custom post types programmatically during theme or plugin development

Configuration

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": ["-y", "wordpress-mcp"],
      "env": {
        "WORDPRESS_URL": "https://your-site.com",
        "WORDPRESS_USERNAME": "admin",
        "WORDPRESS_APP_PASSWORD": "xxxx xxxx xxxx xxxx"
      }
    }
  }
}

Generate an application password from WordPress admin under Users > Your Profile > Application Passwords.

MySQL MCP -- Direct Database Access for the Hard Problems

Author: Community | Tools: 6 | Requires: MySQL credentials

Six tools for MySQL interaction: executing queries, inspecting schemas, listing databases and tables, and running data analysis queries. WordPress stores everything in MySQL -- posts, options, user meta, plugin settings, transients, and serialized data structures. For a comparison with other database servers, see Postgres vs SQLite vs MySQL MCP.

Why use it

• Query a misbehaving plugin's option, unserialize the data, and identify what is wrong without opening phpMyAdmin
• Audit wp_postmeta usage to find orphaned entries from deleted plugins
• Analyze WooCommerce order patterns, inventory data, and pricing calculations directly in the database
• Check which custom fields are actually being used and how many posts have each meta key

Configuration

{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "args": ["-y", "mysql-mcp"],
      "env": {
        "MYSQL_HOST": "localhost",
        "MYSQL_USER": "wp_user",
        "MYSQL_PASSWORD": "your-password",
        "MYSQL_DATABASE": "wordpress_db"
      }
    }
  }
}

Use your local development database credentials. Never point this at production without read-only access.

Filesystem MCP -- Theme and Plugin Development

Author: Anthropic | Tools: 11 | Setup: Zero-config

Eleven tools for file operations: reading contents, listing directories, searching within files, creating files, editing files, and managing the file system. Access is scoped to directories you specify. See the Filesystem MCP guide for detailed setup tips.

Why use it

• Debug template hierarchy issues by reading your theme's file structure and checking which template WordPress selects for a given URL
• Read a third-party plugin's PHP files to understand how it registers custom post types or modifies the main query
• Search all PHP files for every usage of pre_get_posts or any other hook to review for conflicts
• Navigate the WordPress directory structure efficiently when building compatibility layers between plugins

Configuration

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/wordpress/wp-content"
      ]
    }
  }
}

Scope to wp-content for theme and plugin development, or the full WordPress root if you need core files.

GitHub MCP -- Version Control for WordPress Projects

Author: Anthropic | Tools: 20 | Requires: GitHub personal access token

Twenty tools for GitHub: repository contents, issues, pull requests, branches, files, and diffs. Professional WordPress development uses version control for custom themes and plugins. For a deeper look, see the GitHub MCP guide. If you use GitLab, see GitHub vs GitLab MCP.

Why use it

• Triage user-reported issues by cross-referencing them with your plugin's current code
• Review theme PRs for common WordPress mistakes: improper escaping, missing nonces, unregistered scripts
• Generate changelogs based on PR descriptions for plugin releases
• Search across your theme or plugin repo for every hook registration

Configuration

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your-token"
      }
    }
  }
}

Use a token with access to your WordPress project repositories.

Context7 MCP -- WordPress Hooks and Functions, Verified

Author: Upstash | Tools: 2 | Setup: Zero-config (npx)

Two tools: library name resolution and documentation querying. Context7 covers WordPress core functions, hooks, the REST API, and the block editor (Gutenberg) APIs. WordPress has thousands of hooks and functions, and the Gutenberg API evolves rapidly.

Why use it

• Get the current block registration API and correct edit and save function patterns for Gutenberg
• Look up exact WP_Query meta query syntax including meta_type for date comparisons
• Verify that WordPress functions you reference have not been deprecated
• Get correct parameter orders and return types for hooks and filters

Configuration

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}

No API key required.

For the complete pre-configured stack, visit the WordPress Developer Stack. If you are looking for guidance on choosing servers that genuinely help your workflow, see how to choose MCP servers that work.