wordpress-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server (default: 3000, only used with --http) | |
| WORDPRESS_URL | Yes | WordPress site URL (e.g. https://your-site.com) | |
| WORDPRESS_USERNAME | Yes | WordPress username | |
| WORDPRESS_APP_PASSWORD | Yes | Application Password for WordPress |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wp_list_postsA | List WordPress posts with optional filters. Returns post ID, title, status, date, and categories. Use to browse existing content or find posts by keyword. |
| wp_get_postA | Get a single WordPress post with full content, metadata, categories, and tags. Use to inspect post content before editing. |
| wp_create_postA | Create a new WordPress post. Provide title and content (HTML). Optionally set status (draft/publish), categories, and tags. |
| wp_update_postA | Update an existing WordPress post. Change title, content, status, categories, or tags. |
| wp_delete_postA | Delete a WordPress post. Moves to trash by default. |
| wp_list_pagesA | List WordPress pages. Returns page ID, title, status, and parent page. Use to browse site page structure. |
| wp_get_pageA | Get a single WordPress page with full content and metadata. |
| wp_create_pageA | Create a new WordPress page. Provide title and content (HTML). Optionally set parent page for hierarchy. |
| wp_update_pageC | Update an existing WordPress page. |
| wp_delete_pageB | Delete a WordPress page. |
| wp_list_mediaA | List media files in the WordPress library. Returns file URLs, types, and metadata. |
| wp_delete_mediaA | Permanently delete a media file from WordPress. |
| wp_list_commentsA | List comments on WordPress posts. Filter by post ID. |
| wp_create_commentB | Create a new comment on a WordPress post. |
| wp_update_commentA | Update or moderate a comment. Change content or approval status. |
| wp_delete_commentA | Permanently delete a comment. |
| wp_list_categoriesA | List all WordPress categories with post counts. |
| wp_list_tagsB | List all WordPress tags with post counts. |
| wp_list_usersA | List WordPress users with their roles. |
| wp_get_site_infoA | Get WordPress site information: name, description, URL, timezone, and available features. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| manage-content | Guide for managing WordPress posts and pages — list, create, update, and delete content |
| manage-media | Guide for managing WordPress media library, comments, categories, and tags |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| WordPress Server Info | Connection status and available tools for this WordPress MCP server |
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action (e.g., wp_get_page vs wp_list_pages, wp_create_post vs wp_create_comment). There is no ambiguity between tools that operate on different WordPress entities.
All tools follow a strict wp_verb_noun pattern (get, list, create, update, delete) with clear resource names. The convention is consistent across the entire set, making the API highly predictable.
20 tools is slightly heavier than the typical 3-15 range, but each tool corresponds to a specific WordPress operation across posts, pages, comments, media, and taxonomies. The count feels justified for the domain, though it borders on heavy.
Posts, pages, and comments have solid CRUD coverage, but media lacks upload/create and update capabilities, and categories/tags have only list operations. These are notable gaps for a WordPress management server, though core content workflows are supported.