WP Astro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_ASTRO_DB | No | SQLite database path for storing state and cache. | data/wp-astro.db |
| WP_ASTRO_MODE | No | Operational mode: 'router' (3 tools) or 'full' (all tools). | router |
| WP_ASTRO_CONFIG | No | Config file path for site credentials and settings. | config/sites.json |
| WP_ASTRO_LOG_LEVEL | No | Logging level: debug, info, warn, or error. | info |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wp_astro_runA | Execute a WordPress-to-Astro frontend action. Use wp_astro_help to list available actions. Common workflows:
Quick actions:
|
| wp_astro_helpC | List available actions, optionally filtered by category. |
| wp_astro_describeB | Get the full input schema for a specific action. |
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 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.