wordpress-mcp-agent-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp-adapter-discover-abilitiesA | Discover all available WordPress abilities in the system. Returns a list of all registered abilities with their basic information. |
| mcp-adapter-get-ability-infoA | Get detailed information about a specific WordPress ability including its input/output schema, description, and usage examples. |
| mcp-adapter-execute-abilityB | Execute a WordPress ability with the provided parameters. This is the primary execution layer that can run any registered ability. |
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
Each tool has a clearly distinct role: discover lists all abilities, get-ability-info provides details for one, and execute runs an ability. There is no meaningful overlap between any of the three.
All tools share the consistent mcp-adapter- prefix and follow a uniform verb-noun pattern: discover-abilities, get-ability-info, execute-ability. The naming is predictable and easy to reason about.
At three tools, this server is tightly scoped for an adapter bridge: discover, inspect, and execute. Each tool earns its place, and the count is appropriate for the generic execution-layer purpose.
The tool surface fully covers the lifecycle of using a WordPress ability: discovering what exists, getting schema/detail, and executing it. Since execution is the generic entry point for any registered ability, there are no obvious dead ends or missing operations.