Find WordPress plugin opportunities: abandoned, low-rated, or poorly-supported plugins to replace.
An MCP server for finding WordPress plugin opportunities — large, established plugins weakened by abandonment, low ratings, or poor support, i.e. plugins you could realistically replace or out-build. It lets AI agents (Claude, Cursor, Windsurf, etc.) query the WordPress.org plugin directory through the lens of "what's a takeable market here?"
Powered by wpgoldmine.io. All querying runs server-side, so no local database or scraping is required.
// Claude Desktop / any MCP client config
{
"mcpServers": {
"wpgoldmine": {
"command": "npx",
"args": ["-y", "wpgoldmine-mcp"]
}
}
}
list_opportunity_presetsLists the curated opportunity angles you can pass as preset (e.g. abandoned-plugins,
low-rated-popular, beatable-niche, unsupported-plugins, high-opportunity,
newest-opportunities).
find_plugin_opportunitiesReturns a ranked, capped list of plugin opportunities.
| Param | Type | Description |
|---|---|---|
preset | string (optional) | A preset key. Composes with tag. |
tag | string (optional) | Narrow to a niche by WordPress.org tag, e.g. seo, forms, backup. |
ecosystem | wordpress | woocommerce (optional) | Defaults to wordpress. |
min_installs / max_installs | number (optional) | Active-install bounds. |
max_rating | number (optional) | Max rating on a 0–100 scale (lower = more dissatisfied users). |
get_pluginOpportunity snapshot for one plugin by slug: installs, rating, last-updated, support resolution, and opportunity / abandonment / monetization scores.
Example agent uses: "Find abandoned WordPress plugins in the forms niche I could rebuild," "Which popular SEO plugins have the worst ratings?", "Give me the opportunity score for wp-super-cache."
WPGOLDMINE_API_KEY — optional. A WP Goldmine account API token (from your account settings) raises
the result limit and unlocks extra fields. Without it, the server uses the free, capped tier.WPGOLDMINE_API_BASE — override the API base (default https://wpgoldmine.io).{
"mcpServers": {
"wpgoldmine": {
"command": "npx",
"args": ["-y", "wpgoldmine-mcp"],
"env": { "WPGOLDMINE_API_KEY": "wpg_your_token_here" }
}
}
}
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y wpgoldmine-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-bishop81-wpgoldmine-mcp": {
"command": "npx",
"args": [
"-y",
"wpgoldmine-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencewpgoldmine-mcpnpmio.github.Bishop81/wpgoldmine-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.