mcp-rs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_rs_statusA | Show the status of the mcp-rs server itself: version, mode, protocol version, config file, where the log and audit log are written, and the state of each handler and plugin. Use it to check the installed version or to find the log files. |
| wordpress_health_checkB | Perform comprehensive WordPress environment health check |
| get_postsA | Retrieve WordPress posts (published ones by default). Without search, filters or page options, it returns all posts; with them, one page and the total |
| get_pagesA | Retrieve WordPress pages. Without search, filters or page options, it returns all pages; with them, one page and the total |
| get_all_contentB | Retrieve both WordPress posts and pages |
| get_postA | Retrieve a single WordPress post or page by ID, including its full content. By default the content is the editable source (with Gutenberg block markup), which can be passed back to update_post unchanged. |
| create_postA | Create a new WordPress post (basic). Defaults to draft status so nothing is published unintentionally. |
| create_advanced_postC | Create a new WordPress post or page with advanced options |
| get_commentsC | Retrieve WordPress comments |
| upload_mediaA | Upload media file to WordPress. Pass either file_data (base64) or file_path. The filename extension and file content must match mime_type. Size is capped at 10 MiB; with file_data, the transport's message size limit (including base64 overhead) usually applies first |
| get_mediaC | Retrieve WordPress media files |
| get_media_itemA | Retrieve a single WordPress media item by ID |
| update_mediaC | Update WordPress media metadata (title, alt text, caption, description) |
| delete_mediaA | Delete WordPress media file. WordPress does not support moving media to the trash by default, so force: true is usually required |
| create_post_with_featured_imageB | Create a new WordPress post with featured image |
| set_featured_imageB | Set featured image for existing post |
| get_categoriesB | Retrieve WordPress categories |
| create_categoryC | Create a new WordPress category |
| update_categoryC | Update an existing WordPress category |
| delete_categoryC | Delete a WordPress category |
| get_tagsB | Retrieve WordPress tags |
| create_tagB | Create a new WordPress tag |
| update_tagC | Update an existing WordPress tag |
| delete_tagC | Delete a WordPress tag |
| create_post_with_categories_tagsA | Create a new WordPress post with categories and tags. Defaults to draft status so nothing is published unintentionally. |
| update_post_categories_tagsC | Update categories and tags for an existing WordPress post or page |
| update_postC | Update an existing WordPress post or page |
| delete_postC | Delete a WordPress post or page |
| create_post_with_embedsB | Create WordPress post with embedded YouTube videos and social media content |
| get_settingsC | Get WordPress site settings |
| update_settingsC | Update WordPress site settings |
| set_front_pageB | Set a static page as the front page |
| set_front_page_to_postsC | Set front page to show latest posts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| WordPress Posts | All WordPress posts |
| WordPress Comments | All WordPress comments |
| WordPress Categories | All WordPress categories |
| WordPress Tags | All WordPress tags |
TDQS
Scored across 33 tools
Several tools have heavily overlapping purposes: create_post, create_post_with_featured_image, create_post_with_categories_tags, create_advanced_post, and create_post_with_embeds all create posts, differing only by optional features. Retrieval tools also blur together: get_posts, get_all_content, get_post, and get_pages overlap, while get_media and get_media_item are easily confused. An agent would struggle to choose the correct tool without trial and error.
Most names follow a predictable snake_case verb_noun pattern such as get_posts, create_category, update_tag, and delete_media. A few deviate with compound or noun-first forms like wordpress_health_check, mcp_rs_status, and create_post_with_featured_image, but the overall convention remains readable and mostly consistent.
With 33 tools, the surface is heavy for a WordPress content-management server. The count is inflated by redundant post-creation variants and overlapping retrieval tools, so many tools do not clearly earn their place.
Core content operations are well covered: posts and pages can be retrieved, created, updated, and deleted; media and taxonomies have CRUD; settings and front-page configuration are present. However, comments are read-only, and there is no user, plugin, theme, or menu management, leaving notable gaps for broader WordPress administration.