WordPress MCP Python
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_URL | No | WordPress site URL (e.g., https://yoursite.com) | |
| WP_PASSWORD | No | WordPress application password | |
| WP_USERNAME | No | WordPress username for application password authentication | |
| WP_JWT_TOKEN | No | JWT token 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wp_posts_searchC | Search and filter WordPress posts with pagination |
| wp_get_postC | Get a WordPress post by ID |
| wp_add_postC | Add a new WordPress post |
| wp_update_postC | Update a WordPress post by ID |
| wp_delete_postB | Delete a WordPress post by ID |
| wp_pages_searchC | Search and filter WordPress pages |
| wp_get_pageC | Get a WordPress page by ID |
| wp_add_pageC | Add a new WordPress page |
| wp_update_pageC | Update a WordPress page by ID |
| wp_delete_pageC | Delete a WordPress page by ID |
| wp_list_categoriesB | List all WordPress categories |
| wp_add_categoryC | Add a new WordPress category |
| wp_update_categoryC | Update a WordPress category |
| wp_delete_categoryB | Delete a WordPress category |
| wp_list_tagsB | List all WordPress tags |
| wp_add_tagC | Add a new WordPress tag |
| wp_update_tagC | Update a WordPress tag |
| wp_delete_tagD | Delete a WordPress tag |
| wp_users_searchC | Search WordPress users |
| wp_get_userC | Get a WordPress user by ID |
| wp_add_userC | Add a new WordPress user |
| wp_update_userC | Update a WordPress user |
| wp_delete_userC | Delete a WordPress user |
| wp_media_searchC | Search WordPress media items |
| wp_get_mediaC | Get a WordPress media item by ID |
| wp_add_mediaC | Upload a media file to WordPress |
| wp_delete_mediaC | Delete a WordPress media item |
| wp_get_site_infoC | Get WordPress site information |
| wp_get_settingsB | Get WordPress site settings |
| wp_update_settingsC | Update WordPress site settings |
| wc_products_searchC | Search WooCommerce products |
| wc_get_productB | Get WooCommerce product by ID |
| wc_add_productC | Add a WooCommerce product |
| wc_update_productC | Update a WooCommerce product |
| wc_delete_productC | Delete a WooCommerce product |
| wc_list_product_categoriesC | List WooCommerce product categories |
| wc_add_product_categoryC | Add a WooCommerce product category |
| wc_update_product_categoryC | Update a WooCommerce product category |
| wc_delete_product_categoryC | Delete a WooCommerce product category |
| wc_list_product_tagsC | List WooCommerce product tags |
| wc_add_product_tagC | Add a WooCommerce product tag |
| wc_update_product_tagC | Update a WooCommerce product tag |
| wc_delete_product_tagC | Delete a WooCommerce product tag |
| wc_list_product_brandsC | List WooCommerce product brands |
| wc_add_product_brandC | Add a WooCommerce product brand |
| wc_update_product_brandC | Update a WooCommerce product brand |
| wc_delete_product_brandC | Delete a WooCommerce product brand |
| wc_orders_searchC | Search WooCommerce orders |
| wc_get_orderC | Get WooCommerce order by ID |
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 49 tools
Each tool targets a distinct resource (post, page, category, tag, user, media, settings, product, order) and action (search, get, add, update, delete, list), with clear wp_ vs wc_ prefixes separating WordPress and WooCommerce. No two tools appear to serve the same purpose.
The naming follows a consistent prefix_verb_noun pattern (e.g., wp_get_post, wc_add_product) with clear prefixes for WordPress (wp_) and WooCommerce (wc_). A minor deviation is that search operations use plural nouns (wp_posts_search, wc_products_search) while other operations use singular (wp_get_post, wc_get_product).
49 tools is excessive; even for a dual-domain server covering WordPress and WooCommerce, many operations could be consolidated (e.g., generic resource tools or grouped endpoints). The surface is heavy and increases cognitive load for an agent.
Core CRUD is well-covered for posts, pages, categories, tags, users, media, products, and product taxonomies, but notable gaps exist: WooCommerce orders lack create/update/delete, media has no update, and comments, custom post types, and order refunds are missing. These gaps will hinder full lifecycle management.