MCP (Model Context Protocol) server for Local, enabling AI tools like Claude Code to manage WordPress development sites
24 tools with consistent verb-noun naming (list_, get_, create_, delete_, etc.) and complete input schemas. Descriptions are present but brief (avg ~80 chars, below the 194-char baseline). All parameters have type definitions and descriptions. However, output schemas are not documented in the source code, and error handling guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Parameter descriptions lack format constraints and validation rules. Missing dependency hints and recovery guidance.
Change site PHP version
Clone an existing WordPress site to create a copy with a new name
Create a new WordPress site in Local. The site will be created and started automatically. Optionally create from an existing blueprint.
Delete a WordPress site. Requires confirm=true as a safety measure.
Export a site database to a SQL file. Site will be auto-started if not running.
Export a WordPress site to a zip file. Site will be auto-started if not running.
Output schemas not documented. Tool descriptions state what is returned (e.g., 'Get detailed information') but do not specify the response structure, field names, or types. LLMs cannot plan downstream tool calls or extract required data without knowing response shape.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications. Tools marked DESTRUCTIVE (delete_site) or WRITE (start_site, wp_cli) lack machine-readable hints. Agents cannot distinguish safe reads from dangerous mutations without parsing descriptions.
Parameter descriptions lack format constraints and validation rules. E.g., 'site' parameter accepts 'Site name or ID' but does not specify format, length, or character restrictions. 'php_version' accepts '8.2.10' but no pattern or enum of valid versions provided. LLMs cannot validate inputs without explicit constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Get information about Local installation including version, platform, and available tools
Get detailed information about a WordPress site
Get site log files
Import a SQL file into a site database. Site will be auto-started if not running.
Import site from zip file
List all available site blueprints (templates)
List available service versions
List all WordPress sites in Local with their name, ID, status, and domain
Open Adminer database management UI for a site. Site will be auto-started if not running.
Open a WordPress site in the default browser. Site will be auto-started if not running.
Rename a WordPress site
Restart a WordPress site (stops then starts it)
Save a site as a blueprint (template) for creating new sites. Site will be auto-started if not running.
Start a WordPress site
Stop a running WordPress site
Toggle Xdebug for a site
Trust the SSL certificate for a site (may require admin password)
Run a WP-CLI command against a WordPress site. Site will be auto-started if not running.
No error handling guidance. Tool descriptions do not explain what to do if a site is not found, a command fails, or a resource is unavailable. Agents receive raw errors with no recovery path (e.g., 'Site not found' vs 'Site not found. Try list_sites() to see available sites.').
Descriptions are brief (avg ~80 chars, below 194-char baseline). Many lack context for tool selection. E.g., 'Get information about Local installation' does not explain when to call it vs other discovery tools. 'Toggle Xdebug for a site' does not explain what Xdebug is or why an agent would enable it.