ItchWPMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_BASE_URL | Yes | The base URL of the WordPress site, e.g., https://your-wordpress-site.example | |
| WP_USERNAME | Yes | WordPress username for authentication | |
| NODE_OPTIONS | No | Node options, e.g., '--use-system-ca' to use system certificate store on Windows. | --use-system-ca |
| WP_APP_PASSWORD | Yes | WordPress application password | |
| WP_ALLOW_PRODUCTION_WRITES | No | Set to 'true' to allow write operations on production URLs. Default is 'false'. | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wordpress_list_pagesC | List WordPress pages from the configured site. |
| wordpress_list_postsC | List WordPress posts from the configured site. |
| wordpress_get_postC | Get a WordPress post by ID from the configured site. |
| wordpress_get_pageC | Get a WordPress page by ID from the configured site. |
| wordpress_create_postB | Create a WordPress post. Defaults to draft status for safe review before publishing. |
| wordpress_update_postC | Update a WordPress post by ID. |
| wordpress_create_pageA | Create a WordPress page. Defaults to draft status for safe review before publishing. |
| wordpress_clone_pageB | Clone an existing WordPress page into a new draft page. |
| wordpress_update_pageB | Update a WordPress page by ID. Only title, content, excerpt, slug, status, parent, and menu order are supported. |
| wordpress_delete_pageC | Delete or trash a WordPress page. Requires confirmDelete=true. |
| wordpress_delete_postC | Delete or trash a WordPress post. Requires confirmDelete=true. |
| wordpress_update_page_statusB | Update only the status for a WordPress page by ID. |
| wordpress_list_mediaC | List media library items. |
| wordpress_upload_mediaC | Upload a local file to the WordPress media library. |
| wordpress_list_categoriesC | List WordPress post categories. |
| wordpress_create_categoryC | Create a WordPress post category. |
| wordpress_list_tagsC | List WordPress post tags. |
| wordpress_create_tagC | Create a WordPress post tag. |
| wordpress_list_pluginsB | List WordPress plugins if the configured user can access the plugins REST endpoint. |
| wordpress_update_plugin_statusA | Activate or deactivate an installed plugin if the authenticated user has permission. |
| wordpress_get_settingsB | Get general WordPress site settings if the authenticated user has permission. |
| wordpress_update_settingsB | Update general WordPress site settings. Only provided fields are changed. |
| wordpress_list_usersC | List WordPress users if the authenticated user has permission. |
| wordpress_list_menusB | List menus if the WordPress menus REST endpoint is available. |
| wordpress_list_menu_itemsB | List menu items if the WordPress menu-items REST endpoint is available. |
| wordpress_rest_requestB | Advanced escape hatch for WordPress REST API calls. Non-GET requests obey write guards. |
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 26 tools
Each tool targets a distinct WordPress resource and action. There is minimal overlap; even the similar update_page and update_page_status are clearly differentiated by scope.
All tools follow a consistent wordpress_verb_noun pattern (e.g., wordpress_create_page, wordpress_list_posts). No mixing of conventions or ambiguous verbs.
26 tools cover a broad domain including posts, pages, media, menus, plugins, settings, and users. While slightly heavy, each tool serves a clear purpose and the count is justified for comprehensive WordPress management.
CRUD for posts and pages is well-covered, but categories and tags lack delete/update, menus only support listing, and there is no user management beyond listing. These are notable gaps for a complete site administration surface.