Local WPCAUTION
MCP server for WordPress database access via Local by Flywheel
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
🎯 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.
🤔 What's an MCP Server?
Think of MCP (Model Context Protocol) as a secure bridge between AI assistants and your development tools. Instead of copying and pasting database schemas or query results, MCP servers let AI assistants directly interact with your tools while you maintain complete control.
Without MCP: "Hey AI, I think there's a table called wpsomething with a column that might be named usermeta... can you write a query?" With MCP: "Hey AI, check what's in my database and write the exact query I need."
💡 The WordPress Developer's Dilemma
Picture this: You're debugging a LearnDash integration issue. Quiz results aren't syncing properly. You fire up Cursor to help diagnose the problem, but without database access, even the most advanced AI is just making educated guesses about your table structures.
The Real-World Impact
Here's an actual support ticket we were working on. The task was simple: fetch quiz activity data from LearnDash tables.
❌ Before MCP Server (AI Flying Blind):
The AI tried its best, suggesting this query:
$quiz_activities = $wpdb->get_results( $wpdb->prepare( 'SELECT post_id, activity_meta FROM ' . esc_sql( LDLMS_DB::get_table_name( 'user_activity' ) ) . ' WHERE user_id=%d AND activity_type=%s AND activity_status=1 AND activity_completed IS NOT NULL', $user_id, 'quiz' ), ARRAY_A );
Problem? The `acti
b58087472be6OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-local-wp --env MYSQL_PASS=${MYSQL_PASS} -- npx -y @verygoodplugins/[email protected]{
"mcpServers": {
"mcp-local-wp": {
"command": "npx",
"args": [
"-y",
"@verygoodplugins/[email protected]"
],
"env": {
"MYSQL_PASS": "${MYSQL_PASS}"
}
}
}
}Exposed tools (5)
3 read · 1 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
mysql_current_site | read | Get information about the currently connected Local WordPress site, including how it was selected |
mysql_list_sites | read | List all available Local WordPress sites and their running status |
mysql_query | write | Execute a read-only SQL query against the Local WordPress database |
mysql_schema | read | Inspect database schema. Without args: lists tables. With table: shows columns and indexes. |
mysql_write | destructive | Execute write operations (INSERT/UPDATE/DELETE) against the Local WordPress database. UPDATE and DELETE require parameterized WHERE clauses for safety. |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | WARN |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
Provides AI assistants with direct, read-only access to Local by Flywheel WordPress databases
mysql_write
.prettierignore
@modelcontextprotocol/sdk, dotenv, mysql2, @eslint/js, @types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint
Gates applied: no_behavioural_pass.
b58087472be6full audit observations/trust-audit/mcp-server/verygoodplugins__local-wp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | b58087472be6 | CAUTION | B | 89 | first audit |
Questions
What is the Local WP MCP server?
MCP server for WordPress database access via Local by Flywheel
What tools does Local WP expose?
5 in total: 3 read-only, 1 that write, and 1 that can delete or overwrite (mysql_write). Every one is listed on this page with its risk.
Is Local WP safe to connect to an agent?
With care. The audit graded it B (89/100) and found 4 things worth knowing before you trust this server, listed below with the exact line each was found on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Local WP need?
It reads MYSQL_PASS from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Local WP run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @verygoodplugins/mcp-local-wp at 1.1.0.
How current is this page?
The grade is for one exact copy of the source (b58087472be6), read on 2026-10-08. The repository is watched and re-audited when it changes.