Wp MCP Hub
UnclaimedFree local MCP hub for connecting AI clients to multiple WordPress MCP servers.
Install
D:\path\to\wp-mcp-hub\.venv\Scripts\python.exe -m wp_mcp_hub.cli mcpSet up this server
More in AI & ML
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
6 of 6 tools
Documented tools (6)
From project documentation. A server handshake does not verify each tool’s description or behavior.
call_site_tool
invoke one named remote tool on one selected site.
diagnose_sites
concurrently diagnose all or selected sites without invoking remote tools.
get_site
retrieve one site by UUID.
list_site_tools
discover and cache the tools exposed by one site.
list_sites
list configured WordPress sites without credentials.
test_site_connection
test protocol negotiation and read-only discovery.
Tool change history
FAQ
Questions about Wp MCP Hub MCP Server
- How do I connect Wp MCP Hub MCP Server to Claude?
- The listing records `D:\path\to\wp-mcp-hub\.venv\Scripts\python.exe -m wp_mcp_hub.cli mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
- Is Wp MCP Hub MCP Server free?
- The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Wp MCP Hub MCP Server do?
- Wp MCP Hub MCP Server documents 6 tools to the agent, including call_site_tool, diagnose_sites, get_site. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.