AgentSidekick

Better agent tooling for WordPress

Integration gap · Measured demandOverall 54.8 / 100 DERConfidence Medium DERCalculated

1,828 public GitHub issues mention "WordPress mcp" (checked 2026-11-21) SRC, while 155 indexed products mention WordPress DER. On the six weighted components it scores 54.8 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2570.00.25 × 70.0 = 17.50Measured
Competition gap0.2015.00.20 × 15.0 = 3.00Measured
Monetisation0.2035.00.20 × 35.0 = 7.00Heuristic
Growth (relative)0.1576.00.15 × 76.0 = 11.40Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0054.80 → 54.8

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for WordPress access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on WordPress. Only some of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use WordPressHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Open source with paid hosting or supportHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
WordPress (integration)

Evidence for

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 1,828

    1828 public GitHub issues contain the phrase "WordPress mcp" (checked 2026-11-21); that is the 70th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • Growth (relative)MeasuredDERvalue 112

    112 products launched in the last 90 days versus 19 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • FeasibilityHeuristicHEU

    WordPress has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 82

    155 indexed products mention WordPress; 82 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/wordpress/

  • MonetisationHeuristicHEU

    WordPress is not primarily a paid business product. This is a rule of thumb, not revenue data.

  • Competition gapMeasuredDER

    One project holds 70% of the 6,095 GitHub stars in this segment, so there is an established leader to displace.

Existing products

All WordPress products

The most notable profiled products mentioning WordPress (up to 8). 155 indexed in total.

elementor-mcp

MCP serverby msrbuildsHEU

768 GitHub starspushed 2d agoGPL-2.0

Frontman for WordPress

MCP serverby frontman-aiSRC

726 GitHub starspushed 1d agolicence unknown

MainWP

MCP serverby mainwpSRC

33 GitHub starspushed todayGPL-3.0

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
155DER
With a full profile
8+DER
Launches, last 90 days
112 vs 19 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official WordPress server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 155 indexed products mention WordPress; 82 of them have a complete record and a repository pushed in the last 180 days.
  • WordPress is not primarily a paid business product. This is a rule of thumb, not revenue data.
  • One project holds 70% of the 6,095 GitHub stars in this segment, so there is an established leader to displace.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "WordPress mcp" in GitHub issues reflect developers wanting WordPress access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22WordPress%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 1,828 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the WordPress page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .