MCP WordPress Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode | false |
| NODE_ENV | No | Environment mode | development |
| CACHE_TTL | No | Cache TTL in seconds | 3600 |
| CACHE_ENABLED | No | Enable caching | true |
| RATE_LIMIT_ENABLED | No | Enable rate limiting | true |
| WORDPRESS_PASSWORD | No | User password (for JWT or basic auth) | |
| WORDPRESS_SITE_URL | Yes | The URL of the WordPress site | |
| WORDPRESS_USERNAME | Yes | WordPress username | |
| WORDPRESS_AUTH_METHOD | No | Authentication method: app-password, jwt, basic, api-key | app-password |
| WORDPRESS_APP_PASSWORD | Yes | Application password (recommended 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wp_test_authA | Tests the authentication and connectivity for a configured WordPress site with detailed connection diagnostics. Usage Examples:
• Test connection: |
| wp_get_auth_statusB | Gets the current authentication status for a configured WordPress site. |
| wp_switch_auth_methodC | Switches the authentication method for a site for the current session. |
| wp_cache_statsB | Get cache statistics for a WordPress site. |
| wp_cache_clearC | Clear cache for a WordPress site. |
| wp_cache_warmC | Pre-warm cache with essential WordPress data. |
| wp_cache_infoB | Get detailed cache configuration and status information. |
| wp_list_commentsB | Lists comments from a WordPress site, with filters. |
| wp_get_commentB | Retrieves a single comment by its ID. |
| wp_create_commentC | Creates a new comment on a post. |
| wp_update_commentC | Updates an existing comment. |
| wp_delete_commentC | Deletes a comment. |
| wp_approve_commentC | Approves a pending comment. |
| wp_spam_commentC | Marks a comment as spam. |
| wp_list_mediaB | Lists media items from a WordPress site, with filters. |
| wp_get_mediaB | Retrieves a single media item by its ID. |
| wp_upload_mediaC | Uploads a file to the WordPress media library. |
| wp_update_mediaC | Updates the metadata of an existing media item. |
| wp_delete_mediaC | Deletes a media item. |
| wp_list_pagesB | Lists pages from a WordPress site, with filters. |
| wp_get_pageC | Retrieves a single page by its ID. |
| wp_create_pageC | Creates a new page. |
| wp_update_pageC | Updates an existing page. |
| wp_delete_pageC | Deletes a page. |
| wp_get_page_revisionsC | Retrieves revisions for a specific page. |
| wp_performance_statsC | Get real-time performance statistics and metrics |
| wp_performance_historyC | Get historical performance data and trends |
| wp_performance_benchmarkB | Compare current performance against industry benchmarks |
| wp_performance_alertsC | Get performance alerts and anomaly detection results |
| wp_performance_optimizeC | Get optimization recommendations and insights |
| wp_performance_exportC | Export comprehensive performance report |
| wp_list_postsB | Lists posts from a WordPress site with comprehensive filtering options. Supports search, status filtering, and category/tag filtering with enhanced metadata display. Usage Examples:
• Basic listing: |
| wp_get_postB | Retrieves detailed information about a single post including metadata, content statistics, and management links. |
| wp_create_postA | Creates a new WordPress post with comprehensive validation and detailed success feedback including management links. Usage Examples:
• Simple post: |
| wp_update_postB | Updates an existing WordPress post with comprehensive validation and change tracking. All parameters except ID are optional - only provided fields will be updated. Usage Examples:
• Update title: |
| wp_delete_postB | Deletes a WordPress post with options for trash or permanent deletion. Includes safety confirmations and detailed feedback on the deletion action. Usage Examples:
• Trash a post: |
| wp_get_post_revisionsA | Retrieves the revision history for a specific post, including details about changes, dates, and authors for content management and auditing purposes. |
| wp_seo_analyze_contentC | Analyze WordPress post content for SEO optimization opportunities including readability, keyword density, structure, and technical factors |
| wp_seo_generate_metadataC | Generate SEO-optimized metadata including title tags, meta descriptions, OpenGraph, and Twitter Card data |
| wp_seo_bulk_update_metadataC | Update SEO metadata for multiple posts with progress tracking and error handling |
| wp_seo_generate_schemaC | Generate JSON-LD structured data schema for enhanced search results |
| wp_seo_validate_schemaC | Validate JSON-LD schema markup for correctness and compliance |
| wp_seo_suggest_internal_linksC | Analyze content and suggest relevant internal linking opportunities for better SEO |
| wp_seo_site_auditC | Perform comprehensive SEO audit of the WordPress site including technical, content, and performance analysis |
| wp_seo_track_serpC | Track search engine result page positions for target keywords |
| wp_seo_keyword_researchC | Research keywords and get suggestions based on topic and competition analysis |
| wp_seo_test_integrationC | Test SEO plugin integration and detect available SEO plugins on the WordPress site |
| wp_seo_get_live_dataC | Retrieve live SEO data from WordPress including plugin-specific metadata and configurations |
| wp_get_site_settingsB | Retrieves the general settings for a WordPress site. |
| wp_update_site_settingsC | Updates one or more general settings for a WordPress site. |
| wp_search_siteB | Performs a site-wide search for content across posts, pages, and media with comprehensive results and metadata. Usage Examples:
• Search everything: |
| wp_get_application_passwordsC | Lists application passwords for a specific user. |
| wp_create_application_passwordC | Creates a new application password for a user. |
| wp_delete_application_passwordC | Revokes an existing application password. |
| wp_list_categoriesC | Lists categories from a WordPress site. |
| wp_get_categoryB | Retrieves a single category by its ID. |
| wp_create_categoryC | Creates a new category. |
| wp_update_categoryC | Updates an existing category. |
| wp_delete_categoryC | Deletes a category. |
| wp_list_tagsC | Lists tags from a WordPress site. |
| wp_get_tagB | Retrieves a single tag by its ID. |
| wp_create_tagC | Creates a new tag. |
| wp_update_tagC | Updates an existing tag. |
| wp_delete_tagC | Deletes a tag. |
| wp_list_usersA | Lists users from a WordPress site with comprehensive filtering and detailed user information including roles, registration dates, and activity status. Usage Examples:
• List all users: |
| wp_get_userB | Retrieves a single user by their ID. |
| wp_get_current_userA | Retrieves the currently authenticated user with comprehensive profile information including roles, capabilities, and account details. Usage Examples:
• Get current user: |
| wp_create_userC | Creates a new user. |
| wp_update_userC | Updates an existing user. |
| wp_delete_userC | Deletes a user. |
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 70 tools
Each tool targets a distinct resource+action (posts, pages, media, comments, categories, tags, users, settings), so boundaries are mostly clear. Minor overlap exists within clusters like wp_cache_stats vs wp_cache_info and the many SEO/performance analysis tools, but descriptions help differentiate them.
Most tools follow a consistent wp_verb_noun pattern (wp_create_post, wp_list_users, wp_delete_comment). A few deviate to noun-first ordering (wp_performance_stats, wp_cache_stats, wp_cache_clear) and auth tools vary (wp_test_auth, wp_get_auth_status), but the overall convention is predictable.
At 70 tools the surface is very heavy, well beyond the 3-15 sweet spot. While WordPress is a broad domain, the large SEO, performance, and cache clusters inflate the count and increase selection burden.
CRUD coverage is strong and near-complete across the core content types (posts, pages, media, comments, categories, tags, users, settings) plus auth and revisions. Gaps like site/plugin/theme administration and menu management exist but core workflows are well served.