WP Astro MCP
Related Servers
Alternatives to WP Astro MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for WordPress automation that enables users to manage content, themes, and site configurations using AI-driven workflows and the WordPress REST API. It provides a wide array of tools for site planning, management, and optimization compatible with tools like Cursor and Claude.35 npm1ISC
- AlicenseBqualityDmaintenanceComprehensive MCP server to manage WordPress sites via natural language, enabling content creation, SEO, and multi-site administration through AI tools like Claude Desktop.70580 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables ChatGPT to manage WordPress content by creating, updating, retrieving, and deleting posts via the WordPress REST API. It uses FastAPI and Cloudflare Tunnels to provide a secure interface for natural language site administration.-
- AlicenseNot gradedqualityAmaintenanceAI-native static site generator with built-in MCP server and Claude Code integration20MIT
- AlicenseNot gradedqualityBmaintenanceHosted MCP server that bridges Claude.ai with one or more WordPress sites.7 npmISC
- AlicenseNot gradedqualityAmaintenanceTurns any WordPress site into an MCP server, allowing AI clients to directly control files, database, WP-CLI, PHP, content, and more through declarative abilities without writing code.1GPL 2.0
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: wp_astro_describe provides schema details, wp_astro_help lists available actions, and wp_astro_run executes actions. There is no overlap in functionality, and each tool serves a unique role in the workflow.
All tool names follow a consistent wp_astro_ prefix with a descriptive verb suffix (describe, help, run). This pattern is uniform and predictable, making it easy to understand each tool's purpose at a glance.
With only 3 tools, the server feels under-scoped for its apparent purpose of managing WordPress-to-Astro workflows. The common workflows and quick actions listed suggest many operations (e.g., site_add, export_plan, github_push) that are not exposed as individual tools, indicating a significant gap in the tool surface.
The tool set is severely incomplete for the domain. While wp_astro_run can execute actions, the server lacks direct tools for key workflows like site management, export, preview, publishing, and sync operations. Agents must rely on a single execution tool without dedicated interfaces for common tasks, leading to potential failures and confusion.