WordPress MCP Hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_MCP_HUB_WEB_PORT | No | Port for the local web dashboard. | |
| WP_MCP_HUB_LOG_LEVEL | No | Logging level. | |
| WP_MCP_HUB_MAX_CONCURRENCY | No | Maximum concurrency for remote calls. | |
| WP_MCP_HUB_READ_RETRY_ATTEMPTS | No | Number of retry attempts for safe read operations. | |
| WP_MCP_HUB_CONNECT_TIMEOUT_SECONDS | No | Connection timeout in seconds. | |
| WP_MCP_HUB_REQUEST_TIMEOUT_SECONDS | No | Request timeout in seconds. | |
| WP_MCP_HUB_TOKEN_REFRESH_SKEW_SECONDS | No | Skew in seconds for token refresh. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List configured WordPress MCP sites without exposing credentials. |
| get_siteC | Get one configured site by UUID. |
| test_site_connectionB | Test MCP connectivity and read-only discovery for one site. |
| list_site_toolsC | List and cache tools exposed by one remote MCP site. |
| call_site_toolC | Call one remote tool after enforcing its local risk policy. |
| diagnose_sitesC | Run non-writing connectivity and discovery checks concurrently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools are clearly distinct by scope (one site vs all sites) and action (list, get, test, call, diagnose). However, test_site_connection, list_site_tools, and diagnose_sites overlap around connectivity and tool discovery, which could cause occasional misselection.
All tool names use consistent snake_case with a verb-first pattern (list_, get_, test_, call_, diagnose_) and include 'site' or 'sites' where relevant. The convention is predictable throughout.
Six tools is well-scoped for a hub that manages configured WordPress MCP sites, tests connectivity, discovers remote tools, and invokes them. Each tool has a clear role without redundancy.
The set covers listing, getting, testing, discovering remote tools, calling remote tools, and diagnosing sites. Minor gaps exist around site lifecycle management (create/update/delete configured sites) and credential handling, but core workflows are covered.