WordPress Plugin Directory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_MCP_CACHE_DIR | No | Custom directory for downloaded ZIP files | |
| WP_MCP_EXTRACT_DIR | No | Custom directory for extracted plugin files |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pluginsA | Search for WordPress.org plugins by keyword |
| get_plugin_infoC | Get detailed information about a specific plugin |
| download_pluginC | Download a plugin from WordPress.org |
| extract_pluginC | Extract a downloaded plugin ZIP file |
| list_plugin_filesC | List files in an extracted plugin |
| read_plugin_fileB | Read the contents of a specific file from an extracted plugin |
| compare_pluginsB | Compare a local plugin with a WordPress.org plugin |
| get_file_diffB | Get detailed diff for a specific file between local and WordPress.org plugin |
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 8 tools
Each tool targets a distinct operation: search, get info, download, extract, list files, read file, compare, and diff. No two tools overlap in purpose; agents can easily distinguish them.
All tool names follow the verb_noun snake_case pattern consistently (e.g., search_plugins, get_plugin_info, list_plugin_files). No deviations or mixed conventions.
With 8 tools, the set is well-scoped for a plugin directory server. It covers the essential workflow (search, get info, download, extract, browse files) without being bloated or sparse.
The tools cover the full lifecycle of interacting with WordPress.org plugins: searching, retrieving info, downloading, extracting, inspecting files, and comparing with local plugins. No obvious gaps for the intended domain.