
MCP Local WP
Gives Claude read-only access to your Local by Flywheel WordPress database through three tools: mysql_query for executing SELECT statements with parameterized queries, mysql_schema for inspecting table structures and indexes, and mysql_current_site for verifying which Local site you're connected to. The real win is automatic site detection. It parses running mysqld processes and Local configs to find the right socket path, even when Local generates those cryptic site IDs that change on restart. If you're working in multiple Local sites, it detects which one based on your current directory or lets you pin it with SITE_NAME. Reach for this when you're tired of Claude guessing at LearnDash table structures or writing JOIN queries blind against WooCommerce custom tables.
- GitHub stars
- 34
- tools
- 4
- transport
- STDIO
- last updated
- Oct 12, 2026
Tools
4 toolsPublic tool metadata for what this MCP can expose to an agent.
mysql_queryExecute read-only SQL against your Local WordPress database.
Execute read-only SQL against your Local WordPress database.
No parameter schema in public metadata yet.
mysql_schemaInspect database schema using INFORMATION_SCHEMA.
Inspect database schema using INFORMATION_SCHEMA.
No parameter schema in public metadata yet.
mysql_current_siteGet information about the currently connected Local WordPress site.
Get information about the currently connected Local WordPress site.
No parameter schema in public metadata yet.
mysql_list_sitesList all available Local WordPress sites and their running status.
List all available Local WordPress sites and their running status.
No parameter schema in public metadata yet.
Sponsors
Readme
MCP Server Local WP
🎯 What if your AI assistant could actually SEE your WordPress database?
A Model Context Protocol (MCP) server that gives AI assistants like Claude and Cursor direct, read-only access to your Local by Flywheel WordPress database. No more guessing table structures. No more writing SQL queries blind. Your AI can now understand your actual data.
Upgrading to 2.0
Version 2.0 requires Node.js 24 or newer and uses MCP SDK v2. Existing tool names and site selectors remain available. Query results are now { "rows": [...] }; schema listing returns { "tables": [...], "hasMore": false, "nextAfter": null } with bounded pages of table names. Successful tools return matching structured and JSON-text results, and failures set isError: true.
Database and Local configuration are resolved lazily, so MCP tool discovery works without a running site. Explicit MYSQL_HOST or MYSQL_SOCKET_PATH selects the manual connection. Keep stdin open until all tool responses arrive; EOF closes the session. The parent watchdog also cleans up abandoned stdio servers.
🤔 What's an MCP Server?
Details
- Repository
- github.com/verygoodplugins/mcp-local-wp
- Website
- verygoodplugins.com/?utm_source=mcp-registry
- Category
- Databases
- Package
@verygoodplugins/mcp-local-wp- Transport
- STDIO
- Registry
- MCP registry, active