From 0972556b381adf497dee093e5015144b48d4b3b9 Mon Sep 17 00:00:00 2001
From: Charles N Wyble <charles@ultix.knel.net>
Date: Tue, 17 Feb 2026 11:38:57 -0500
Subject: [PATCH] docs: add terraform-ls and wordpress-mcp status to STATUS.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Add terraform-ls to detailed status table (Built, v0.38.4)
- Document wordpress-mcp as Blocked (requires WordPress instance)
- Add Known Issues section for WordPress MCP Adapter architecture
- Update MCP Servers with Configuration Issues section

🧡 Generated with Crush

Assisted-by: GLM-5 via Crush <crush@charm.land>
---
 STATUS.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/STATUS.md b/STATUS.md
index d016a67..fbbf366 100644
--- a/STATUS.md
+++ b/STATUS.md
@@ -26,6 +26,7 @@ Last validated: 2026-02-17
 **MCP Servers with Configuration Issues:**
 - ✗ imap-mcp: Not working - requires working IMAP server (server crashes on startup if IMAP unreachable)
 - ✗ webserial-mcp: Not working - requires bridge server (esp32_bridge_server.py) running at ws://host.docker.internal:3000 + browser with WebSerial access + ESP32 hardware
+- ✗ wordpress-mcp: Blocked - requires WordPress instance (PHP plugin, not standalone MCP server)
 
 **Host-Only MCP Servers:**
 - ✗ kicad-mcp: Requires KiCAD installed on host (pcbnew Python module unavailable in container)
@@ -112,6 +113,8 @@ All the following ahujasid repositories exist but contain no code (empty repos w
 | bash-language-server | Built | Container built using prebuilt npm package (190MB). LSP configured in crush.json via wrapper script. Version 5.6.0. |
 | docker-language-server | Built | Container built from Go source (49.2MB). LSP configured in crush.json via wrapper script. Version 0.0.0. |
 | marksman | Built | Container built from prebuilt binary (144MB). LSP configured in crush.json via wrapper script. Version 2025-12-13. |
+| terraform-ls | Built | Container built from HashiCorp binary (64MB). LSP configured in crush.json via wrapper script. Version 0.38.4. |
+| wordpress-mcp | Blocked | Cannot build as standalone MCP server. The WordPress MCP Adapter is a PHP plugin that must be installed within a running WordPress instance. Requires WordPress + Abilities API plugin + MCP Adapter plugin. Uses WP-CLI for STDIO transport. Not suitable for containerized standalone deployment. |
 
 ## Known Issues
 
@@ -126,6 +129,15 @@ These repos cannot be used to build MCP containers. Alternative sources or offic
 ### Alternative Repositories Available
 - kubernetes-mcp: Use silenceper/mcp-k8s instead (has content and Dockerfile)
 
+### WordPress MCP Configuration (2026-02-17)
+The WordPress MCP Adapter (`@wordpress/mcp-adapter`) is NOT a standalone MCP server:
+- It is a PHP plugin that must be installed within a running WordPress instance
+- Requires the WordPress Abilities API plugin (`wordpress/abilities-api`)
+- Uses WP-CLI for STDIO transport: `wp mcp-adapter serve --user=admin --server=mcp-adapter-default-server`
+- HTTP transport available via `/wp-json/mcp/mcp-adapter-default-server`
+- The docker-compose.yml entry for wordpress-mcp needs to be reconfigured or removed
+- For containerized use, would need a full WordPress + plugins image, not just the MCP adapter
+
 ### Previously Documented Issues
 - matomo-mcp: Vendor repository does not exist. The CloneVendorRepos.sh references `https://github.com/ahujasid/matomo-mcp-client.git` which returns 404. Unable to build until a valid source is identified.
 - discourse-mcp: Vendor repository exists but is empty. The CloneVendorRepos.sh references `https://github.com/ahujasid/discourse-mcp.git` which has no commits. Unable to build until repository has content.