Local WP FAQs

Question 1

Is the database access read-only?

Accepted Answer

Yes, Local WP strictly enforces read-only access to your WordPress database. It only supports SQL commands like SELECT, SHOW, DESCRIBE, and EXPLAIN, ensuring the integrity and safety of your development data.

Question 2

Can Local WP handle custom tables from WordPress plugins?

Accepted Answer

Absolutely. Local WP inspects the actual database schema, meaning your AI assistant will understand and adapt to any custom tables introduced by plugins like WooCommerce, LearnDash, or others, allowing for accurate, plugin-aware queries.

Question 3

What specific challenges does Local WP solve for Local by Flywheel users?

Accepted Answer

Local WP automatically detects and connects to your active Local by Flywheel MySQL instance. This solves common issues like dynamic socket paths, changing site IDs, and complex configuration, providing a seamless and maintenance-free connection for AI assistants.

Question 4

How does Local WP improve AI assistant capabilities for WordPress development?

Accepted Answer

It eliminates the need for AI to guess database structures or column names. By giving AI real-time access to your actual database schema, including custom plugin tables (e.g., WooCommerce, LearnDash), it enables AI to generate precise SQL queries, understand table relationships, and significantly speed up debugging and development tasks.

Question 5

What is Local WP and what does it do?

Accepted Answer

Local WP is a Model Context Protocol (MCP) server that provides AI assistants (like Claude and Cursor) with direct, read-only access to your Local by Flywheel WordPress development databases. It allows AI to 'see' your database schema, understand table structures, and write accurate SQL queries.

Local WP

Local WP

Key Features

Use Cases

Key Features

Use Cases