WordPress MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORDPRESS_URL | Yes | Your WordPress site URL (e.g., https://example.com) | |
| WORDPRESS_USER | Yes | WordPress username | |
| WORDPRESS_APP_PASSWORD | Yes | Application password (not your login password!) |
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 |
|---|---|
| wp_get_postsA | Get posts from WordPress. |
| wp_get_pagesA | Get pages from WordPress. |
| wp_get_mediaA | Get media items from WordPress media library. |
| wp_get_pluginsA | Get installed plugins from WordPress. Requires authentication. |
| wp_site_infoB | Get WordPress site information. |
| wp_get_postA | Get a single post by ID with full content. |
| wp_create_postA | Create a new WordPress post. |
| wp_update_postA | Update an existing WordPress post. |
| wp_delete_postA | Delete a WordPress post. |
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 9 tools
Every tool has a clearly distinct purpose targeting specific WordPress resources and actions. There is no ambiguity between tools like wp_get_post (single post retrieval), wp_get_posts (multiple posts listing), wp_get_pages (pages listing), and wp_get_media (media library access). Each tool's name and description make its unique function immediately apparent.
All tools follow a perfect wp_verb_noun naming pattern throughout the entire set. The structure is consistently snake_case with clear action verbs (create, delete, get, update) followed by specific nouns (post, media, pages, plugins, site_info). This predictable naming convention makes the tool set highly readable and discoverable.
With 9 tools, this server is well-scoped for WordPress content management. Each tool earns its place by covering essential WordPress operations: post CRUD (create, get, update, delete), content listing (posts, pages, media), plugin management, and site information. The count is neither too sparse nor bloated, providing comprehensive coverage without overwhelming complexity.
The tool set provides excellent coverage for WordPress content management with complete post lifecycle operations and key content retrieval functions. Minor gaps exist: there's no media upload/creation tool, no page creation/update/delete operations, and no user management tools. However, the core post workflow is fully covered, and agents can work effectively with the provided surface.