WordPress MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_FILE | No | Optional path to log file | |
| JWT_TOKEN | No | Your JWT token for authentication | |
| WP_API_URL | No | The WordPress site URL | |
| WP_API_PASSWORD | No | Your application password for authentication | |
| WP_API_USERNAME | No | Your WordPress username for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-postsC | Search for WordPress posts by title or keyword |
| get-postC | Get a WordPress post by its ID |
| create-postC | Create a new WordPress post using Gutenberg blocks |
| update-postC | Update a WordPress post using Gutenberg blocks |
| wordpress-block-types-schemaC | Available WordPress block types that can be used for content creation |
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 5 tools
Each tool has a clearly distinct purpose: create-post, get-post, search-posts, and update-post cover different CRUD operations for posts, while wordpress-block-types-schema provides metadata for content creation. There is no overlap or ambiguity between these tools.
Four tools follow a consistent verb-noun pattern (create-post, get-post, search-posts, update-post), but wordpress-block-types-schema deviates with a longer, descriptive name. This minor inconsistency slightly reduces the overall naming coherence.
With 5 tools, this server is well-scoped for managing WordPress posts. The count is appropriate for the domain, covering core operations without being overly sparse or bloated, and each tool serves a clear purpose.
The tool set provides good coverage for WordPress post management with create, read, update, and search operations, plus block type information. A minor gap is the lack of a delete-post tool, which agents might need to work around, but core workflows are well-supported.