Pull WordPress plugin reviews and rankings via API or MCP
WordPress.org publishes plugin metadata, but tracking review history, active-installation growth and search position over time means collecting and storing it yourself. SaaS Review Tracker does that for the plugins you add and exposes everything through a REST API and an MCP server.
What data you can pull
| Field | Type | Description |
|---|---|---|
| name | string | Display name of the tracked profile. |
| average_rating | number | Current average star rating. |
| total_reviews | number | Total number of reviews counted on the profile. |
| reviews[] | array | Individual reviews: rating, title, body, author, review date, vendor reply. |
| snapshots[] | array | Historical daily/weekly/monthly snapshots of rating and review count. |
| last_scraped_at | timestamp | When the profile was last refreshed. |
| active_installations | number | Active installation count reported by the directory. |
| star_distribution | object | Share of 5/4/3/2/1-star reviews on the plugin page. |
Rankings: WordPress.org search rankings: your plugin’s position for each tracked keyword in the plugin directory search results, tracked over time.
Pull WordPress.org Plugin Directory reviews with the REST API
Every request is authenticated with a personal API key sent in the x-api-key header. The slug parameter is the Plugin slug (from the wordpress.org/plugins/<slug> URL).
List tracked WordPress.org Plugin Directory profiles
curl "https://reviews.saas.group/api/v1/get-entity-data?type=wordpress" \
-H "x-api-key: YOUR_API_KEY"Get one profile with reviews and history
curl "https://reviews.saas.group/api/v1/get-entity-data?type=wordpress&slug=juicer&include=reviews,snapshots&reviews_limit=25" \
-H "x-api-key: YOUR_API_KEY"Example response
{
"success": true,
"type": "wordpress",
"entity": {
"name": "Juicer",
"slug": "juicer",
"average_rating": 4.8,
"total_reviews": 320,
"last_scraped_at": "2026-08-24T06:00:00Z"
},
"reviews": [
{
"rating": 5,
"title": "<review title>",
"body": "<review body text>",
"author_name": "<reviewer name>",
"review_date": "2026-08-21",
"vendor_reply": "<vendor response, when present>"
}
],
"snapshots": [
{ "average_rating": 4.8, "total_reviews": 318, "scraped_at": "2026-08-17T06:00:00Z" }
],
"reviews_page": { "limit": 25, "returned": 25, "total": 320, "has_more": true, "next_cursor": "eyJkIjoi..." }
}Reviews and snapshots paginate independently. Follow reviews_page.next_cursor and snapshots_page.next_cursor until has_more is false.
Read WordPress.org Plugin Directory data from an AI assistant via MCP
The Model Context Protocol server lets Claude Desktop, Cursor, ChatGPT, n8n and other MCP clients query the same data in natural language. Endpoint: https://reviews.saas.group/api/v1/mcp
Client configuration
{
"mcpServers": {
"saas-tracker": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://reviews-mcp.saas.group/mcp",
"--header", "x-api-key:YOUR_API_KEY"
]
}
}
}Tool calls for WordPress.org Plugin Directory
// get_entity
{ "type": "wordpress", "slug": "juicer", "include": ["reviews", "snapshots"], "mode": "summary" }
// list_entities
{ "type": "wordpress", "limit": 50 }
// list_rankings — keyword/category ranking history
{ "type": "wordpress", "slug": "juicer", "limit": 50 }
// add_entity — start tracking a new profile
{ "type": "wordpress", "identifier": "https://wordpress.org/plugins/juicer/" }
// get_scrape_status — poll until ready: true
{ "type": "wordpress", "slug": "juicer" }
// refresh_entity — queue a fresh scrape (max 1 per 10 min)
{ "type": "wordpress", "slug": "juicer" }Available tools: list_channels, list_entities, get_entity, list_rankings, add_entity, get_scrape_status and refresh_entity. Once connected you can simply ask, for example, “summarise the newest WordPress.org Plugin Directory reviews for Juicer”.
list_rankings is available for WordPress.org Plugin Directory and returns rank history newest-first, optionally filtered to a single keyword or category.
Add a new WordPress.org Plugin Directory profile via API or MCP
You can start tracking a profile without opening the app. Pass the public profile URL (or the bare plugin slug (from the wordpress.org/plugins/<slug> url)) to add_entity. Accepted identifier formats: wordpress.org/plugins/<slug> or a bare slug. The first scrape runs in the background, so poll get_scrape_status until it returns ready: true before reading reviews. Regular accounts can track up to three profiles in total.
# 1. start tracking a profile
curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"action":"add","type":"wordpress","identifier":"https://wordpress.org/plugins/juicer/"}'
# 2. poll until the first scrape finishes
curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"action":"status","type":"wordpress","slug":"juicer"}'
# 3. queue a later refresh (max one per 10 minutes)
curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"action":"refresh","type":"wordpress","slug":"juicer"}'If the profile is already tracked, the call succeeds with already_exists: true and returns the existing record. A refresh requested within 10 minutes of the last scrape returns 429; a profile another account tracks privately returns 403.
Access and data scope
Every account gets REST API and MCP access, and each account uses its own key.
A key reads the public profiles (saas.group and example profiles) plus the profiles and keywords that account tracks. Profiles you add stay private to you. An administrator can widen an account’s data scope to all tracked entities.
Create an account to start tracking WordPress.org Plugin Directory profiles, then open the API & MCP reference to generate your key.

OMR Reviews