A
licenseB
qualityB
maintenanceEnables AI assistants to manage WordPress sites via the MainWP Dashboard REST API, providing tools for site health monitoring, updates, plugin/theme management, and client/cost tracking.
43
13 npm
1
MIT
MainWP MCP Server
Officialby mainwp
Related Servers
Alternatives to MainWP MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to manage WordPress content, design, SEO, WooCommerce, and more through natural language commands.1005 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.9MIT
- FlicenseNot gradedqualityAmaintenanceExposes MainWP Dashboard site-management operations as an MCP server for AI agents, with policy-controlled tools, safe-mode destructive protections, confirmation workflows, and guided prompts for troubleshooting, maintenance, updates, and security.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage and interact with WordPress sites through MCP, providing tools for content creation, moderation, WooCommerce operations, and governance.47GPL 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct roles: one is a read-only status/diagnostic reporter and the other performs the one-time configuration write. An agent can unambiguously pick between 'tell me the state' and 'set up the connection' without overlap.
Naming Consistency4/5
Both names use the same mainwp_ snake_case prefix, which is consistent. The only minor deviation is the verb form: one uses the get_ verb convention while the other is a bare action name (mainwp_configure).
Tool Count3/5
Two tools is very thin for a server branded as full MainWP management; the surface only covers connection onboarding (status + configure). It is defensible if the scope is intentionally setup-only, but it sits at the borderline-thin end of the range.
Completeness3/5
Onboarding is covered by status and configure, but there is no way to disconnect, reset, or update credentials once connected (configure is explicitly only usable before connection). That leaves a notable lifecycle gap with no recovery path for bad or rotated credentials.
Maintenance
ActivityMaintained
ResponsivenessSlow