MCP server for BugLens — connect AI coding agents to WordPress sites on shared hosting
BugLens MCP has 20 tools with mostly complete schemas and descriptions. Naming is verb-first and clear (read_file, write_file, batch_write, etc.). Descriptions are present and actionable (avg ~120 chars), exceeding the 10-char minimum. Zod schemas are properly typed with descriptions for all parameters. However, several critical gaps reduce the score: (1) No output schemas documented, tools return text responses but the structure of returned JSON is not formally specified, forcing LLMs to parse unstructured output. (2) Error handling is minimal, no recovery guidance, no categorization of retryable vs fatal errors, no actionable error messages. (3) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). (4) Batch operations (batch_write, verify_files) lack per-item success/failure reporting. (5) No pagination support on list_directory or search_files despite potential for large result sets. (6) Missing parameter constraints: search_files max_results defaults to 100 but no min/max bounds stated; directory_tree depth 1-10 is constrained but not validated in description.
Atomically write multiple files (all-or-nothing, max 50 files, 10MB total). Prevents partial-deploy disasters where N files succeed but N+1 fails.
Read multiple files at once (max 20)
Create a new file or directory on the WordPress site
Delete a file or empty directory from the WordPress site
Compare content against the current file on disk
Get a tree view of the directory structure
No output schemas documented. Tools return text responses with embedded JSON, but the structure of returned objects (e.g., batch_write response fields, health_check diagnostic snapshot structure) is not formally specified. LLMs must parse unstructured text, increasing errors and token waste.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels assigned in metadata. Tools like delete_file (DESTRUCTIVE) and batch_write (WRITE) should declare their side effects so agents can reason about safety and retry semantics.
Minimal error handling. No recovery guidance, no error categorization (retryable vs fatal), no actionable error messages. E.g., if batch_write fails on file 5 of 50, the response does not indicate which files succeeded/failed or how to retry.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Get metadata about a file or directory (size, permissions, modified date)
Get full details of a specific BugLens bug report
List all BugLens bug reports
Diagnostic snapshot — WP boot status, PHP/MySQL versions, memory, error log tail, rescue mode status. Use before risky deploys.
List contents of a directory on the WordPress site
Dry-run validate paths (parent exists? writable? blocked?) without any file changes. Use before /batch_write.
Read the contents of a file from the WordPress site
Rename or move a file/directory on the WordPress site
EMERGENCY: Call rescue.php directly (bypasses WP REST). Use only when WP is in fatal-error state (REST endpoints return 500). Requires BUGLENS_RESCUE_URL + BUGLENS_RESCUE_KEY env vars.
Search for text/pattern across files on the WordPress site (like grep)
Update the status of a BugLens bug report
Bulk verify file existence + SHA256 hashes. Use for pre/post-deploy assertions.
Execute a WP-CLI command on the WordPress site (if available)
Write content to an existing file on the WordPress site
No pagination support on list_directory or search_files despite potential for large result sets. search_files defaults to max_results=100 but offers no cursor/offset for continuation. Large WordPress sites could return 100+ matches, exhausting context.
wp_cli description is vague ('Execute a WP-CLI command') and lacks guidance on which commands are safe vs dangerous. No examples, no list of supported commands, no warning about irreversible operations like 'wp db reset'.