WordPress MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORDPRESS_SITE | Yes | The full URL to your WordPress site (with https:// or http://) | |
| WORDPRESS_PASSWORD | Yes | The application password you created (NOT your regular WordPress password) | |
| WORDPRESS_USERNAME | Yes | Your WordPress username (not email) |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_postsA | List posts in WordPress site and get basic information of each post. Date parameters must be valid ISO 8601 date strings (YYYY-MM-DDTHH:MM:SS). |
| retrieve_postB | Retrieve all metadata of a post in WordPress site. |
| create_postA | Create a post in WordPress site. Use HTML tags to format the content, for example, Bold Text for bold text. By default, the post will be created as a draft. Do NOT set status to publish unless it is confirmed by the user. Date must be ISO 8601 format. Future dates will schedule the post. |
| update_postA | Update a post in WordPress site. Only provided fields will be updated. Use HTML tags for content formatting. Date must be ISO 8601 format. |
| delete_postA | Delete a post in WordPress site. If force=false, post is moved to trash. If force=true, post is permanently deleted. |
| list_usersA | List users in WordPress site. Only admin users have permission to do this. |
| get_meA | Get all metadata of the current user in WordPress site, including roles and capabilities. Failed to get user info indicates authentication is not working correctly. |
| validate_credentialA | Validate WordPress credentials by attempting to get current user profile. This is useful for testing authentication before performing other operations. |
| list_mediaB | List media files in WordPress site and get basic information of each media file. Date parameters must be valid ISO 8601 date strings (YYYY-MM-DDTHH:MM:SS). |
| update_mediaA | Update the metadata of a media file in WordPress site. At least one field must be provided to update. |
| delete_mediaB | Delete a media file in WordPress site. |
| list_categoriesC | List available categories in WordPress site. |
| create_categoryB | Create a new category in WordPress site. |
| update_categoryA | Update an existing category in WordPress site. Only provided fields will be updated. At least one field must be provided to update. |
| delete_categoryA | Delete a category in WordPress site. Posts previously assigned to this category will be moved to 'Uncategorized'. |
| list_tagsC | List available tags in WordPress site. |
| create_tagB | Create a new tag in WordPress site. |
| update_tagA | Update an existing tag in WordPress site. Only provided fields will be updated. At least one field must be provided to update. |
| delete_tagA | Delete a tag in WordPress site. Posts previously assigned to this tag will no longer have it. |
| get_site_settingsA | Get the settings of the WordPress site. Only admin users have permission to do this. Returns basic site information and settings that are publicly available or accessible to authenticated users with appropriate permissions. |
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 20 tools
Each tool targets a distinct resource (post, user, media, category, tag, settings) with a unique action. There is no ambiguity—tools clearly differ by resource and operation.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_posts, create_category), making them predictable and easy for an agent to understand.
With 20 tools, the server covers essential CRUD for posts, categories, tags, and media, plus user info and settings. The scope is appropriate for a WordPress management server without being bloated.
Posts, categories, and tags have full CRUD, but media lacks a create (upload) tool, and user management is limited to listing and current user info—missing user creation, update, and deletion.