# WordPress.org Plugins & Themes Directory Data (`shawndunn/wordpress-plugins-themes-directory`) Actor Active installs, downloads, ratings, support-thread resolution, versions and compatibility for WordPress.org plugins or themes, by search, slug or popular lists. Extracts fields: type, query, slug, name, version, author, activeInstalls, downloaded, rating, numRatings, oneStarRatings, supportThreads. - **URL**: https://apify.com/shawndunn/wordpress-plugins-themes-directory.md - **Developed by:** [CarrierDaily](https://apify.com/shawndunn) (community) - **Categories:** Developer tools - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $0.50 / 1,000 plugins This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## WordPress.org Plugins & Themes Directory Data Active installs, downloads, ratings, support-thread resolution, versions and compatibility for WordPress.org plugins or themes, by search, slug or popular lists. ### Why this actor - Includes support-resolution and 1-star counts for quality screening. - Pay only for results: **$0.50 per 1,000 plugins**, no start fee, failed lookups are free. - Robust: automatic retries with exponential backoff, respects `Retry-After`, per-item error rows instead of crashed runs. - Clean, flat JSON/CSV/Excel output ready for Google Sheets, Make, Zapier, n8n, Clay, or the Apify API. ### Use cases - Plugin market research - Find acquisition targets - Agency vendor vetting ### How to use WordPress.org Plugins & Themes Directory Data 1. Configure `searchTerms`, `slugs`, `browse` in the Input tab (or leave the prefilled sample values to test immediately). 2. Optionally set `maxItems` to cap the number of results and control spend. 3. Click **Start** and export structured results as JSON, CSV, Excel, or connect directly via API / MCP / n8n / Make. ### Input | Field | Type | Description | |---|---|---| | `searchTerms` | array | Keywords. | | `slugs` | array | Exact plugin/theme slugs (e.g. woocommerce). | | `browse` | string | Directory list instead of search. | | `type` | string | Plugins or themes. | | `maxPerQuery` | integer | Cap. | | `maxItems` | integer | 0 = no limit. Caps cost. | Example input: ```json { "searchTerms": [ "seo" ] } ``` ### Output Each dataset item looks like this (real sample from a test run, long fields trimmed): ```json { "type": "plugin", "query": "woocommerce", "slug": "woocommerce", "name": "WooCommerce", "version": "11.2.1", "author": "Automattic", "activeInstalls": 7000000, "downloaded": null, "rating": 4.5, "numRatings": 4826, "oneStarRatings": 410, "supportThreads": 147, "supportResolved": 129, "requiresWp": "7.0", "testedWp": "7.1.3", "requiresPhp": "7.4", "lastUpdated": "2026-10-09 3:35pm GMT", "added": "2011-09-27", "tags": [ "ecommerce", "online store", "sell online", "\u2026" ], "homepage": "https://woocommerce.com/", "shortDescription": null, "url": "https://wordpress.org/plugins/woocommerce/", "fetchedAt": "2026-10-15T00:07:04+00:00" } ``` Rows that could not be processed contain an `error` field and are **not charged**. ### Extracted output fields Every dataset row includes structured fields ready for spreadsheets, CRMs, and AI pipelines: - **Fields**: `type`, `query`, `slug`, `name`, `version`, `author`, `activeInstalls`, `downloaded`, `rating`, `numRatings`, `oneStarRatings`, `supportThreads`, `supportResolved`, `requiresWp`, `testedWp`, `requiresPhp`, `lastUpdated`, `added`, `tags`, `homepage`, `shortDescription`, `url`, `fetchedAt` ### Comparison: WordPress.org Plugins & Themes Directory Data vs alternatives | Feature | This Actor (`shawndunn/wordpress-plugins-themes-directory`) | Typical alternatives | |---|---|---| | Pricing model | **$0.50 / 1,000 results**, $0.00 start fee | $20–$49/mo subscription or per-run start fees | | Failed / error lookups | **$0.00 (never charged)** | Often billed by compute time even on failures | | API keys / proxies required | **None** (works out of the box) | Often requires paid third-party keys or residential proxies | | AI Agent & MCP ready | **Yes** (`mcp.apify.com` compatible, optional defaults) | Strict required schemas that reject agent calls | ### Pricing Pay-per-event: **$0.0005** per plugin (= $0.50 / 1,000). Use **Max results** to cap spend. Apify's free plan credit covers thousands of results per month. ### Integrations & API Run on a schedule in Apify Console, call via the Apify API / Python & JS clients, or connect to Make, Zapier, n8n, Google Sheets, Slack and webhooks. Works as a tool for AI agents via Apify MCP. ### Use with AI agents (MCP) WordPress.org Plugins & Themes Directory Data is configured for zero-config AI agent tool use via the Apify MCP Server (no required-field blocking on defaulted inputs). Streamable HTTP endpoint: ```text https://mcp.apify.com/?tools=shawndunn/wordpress-plugins-themes-directory ``` Claude Desktop / Cursor / Windsurf `mcpServers` config: ```json { "mcpServers": { "apify-wordpress-plugins-themes-directory": { "url": "https://mcp.apify.com/?tools=shawndunn/wordpress-plugins-themes-directory", "headers": { "Authorization": "Bearer " } } } } ``` Direct synchronous API call: ```text POST https://api.apify.com/v2/acts/shawndunn~wordpress-plugins-themes-directory/run-sync-get-dataset-items?token= ``` ### FAQ **Is this an official tool?** No. It is an independent actor and is not affiliated with, sponsored or endorsed by the data source or any trademark owner named here. **Is it legal?** The actor only reads publicly available data from public endpoints, without logins, and does not bypass paywalls or access controls. You are responsible for using the data in line with applicable laws (e.g. GDPR) and the source sites' terms. **Something broke?** Open an issue in the Issues tab; we typically respond within 24 hours and ship fixes fast. ### More tools by shawndunn - [Website Tech Stack Detector](https://apify.com/shawndunn/website-tech-stack-detector) — Find what CMS, ecommerce platform, analytics, pixels and frameworks any website uses. - [Domain Intelligence Checker](https://apify.com/shawndunn/domain-intelligence-whois-dns-ssl) — Bulk domain lookup: WHOIS/RDAP registrar and expiry dates, DNS, MX email provider, SPF, DMARC and SSL certificate expiry. - [Bulk PageSpeed Insights & Core Web Vitals Checker (Lighthouse)](https://apify.com/shawndunn/bulk-pagespeed-core-web-vitals) — Audit hundreds of URLs with Google PageSpeed Insights: performance, SEO, accessibility and best-practices scores, LCP, CLS, TBT ($3/1k, no start fee). - [Sitemap URL Extractor](https://apify.com/shawndunn/sitemap-url-extractor) — Extract every URL from any website's XML sitemaps: auto-discovery via robots. - [Broken Link Checker & Bulk URL Status Checker](https://apify.com/shawndunn/broken-link-checker) — Crawl a website and test every internal and external link, or bulk-check a list of URLs (url, statusCode, ok, finalUrl) ($1/1k, no start fee). # Actor input Schema ## `searchTerms` (type: `array`): Keywords. ## `slugs` (type: `array`): Exact plugin/theme slugs (e.g. woocommerce). ## `browse` (type: `string`): Directory list instead of search. ## `type` (type: `string`): Plugins or themes. ## `maxPerQuery` (type: `integer`): Cap. ## `maxItems` (type: `integer`): 0 = no limit. Caps cost. ## Actor input object example ```json { "searchTerms": [ "seo" ], "type": "plugin", "maxPerQuery": 100, "maxItems": 0 } ``` # Actor output Schema ## `overview` (type: `string`): No description ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searchTerms": [ "seo" ] }; // Run the Actor and wait for it to finish const run = await client.actor("shawndunn/wordpress-plugins-themes-directory").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searchTerms": ["seo"] } # Run the Actor and wait for it to finish run = client.actor("shawndunn/wordpress-plugins-themes-directory").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "searchTerms": [ "seo" ] }' | apify call shawndunn/wordpress-plugins-themes-directory --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,shawndunn/wordpress-plugins-themes-directory" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/dZq3I158qE1pby35d/builds/xGe3eNOzgpxU7Kj4o/openapi.json