AgentSidekick

Better agent tooling for Webflow

Integration gap · Measured demandOverall 53.0 / 100 DERConfidence Low DERCalculated

123 public GitHub issues mention "Webflow mcp" (checked 2026-11-21) SRC, while 3 indexed products mention Webflow DER. On the six weighted components it scores 53.0 of 100, confidence Low, as of 2026-11-21.

Score breakdown

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

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2512.00.25 × 12.0 = 3.00Measured
Competition gap0.2098.00.20 × 98.0 = 19.60Measured
Monetisation0.2035.00.20 × 35.0 = 7.00Heuristic
Growth (relative)0.1550.00.15 × 50.0 = 7.50Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0053.00 → 53.0

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

Confidence: Low

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

  • At least 10 indexed products mentioning Webflow (now 3), so the gap is measured on a real population.

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 Webflow 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 Webflow. Very few of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use WebflowHEU
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
LowDER
Subject
Webflow (integration)

Evidence for

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 1

    3 indexed products mention Webflow; 1 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/webflow/

  • FeasibilityHeuristicHEU

    Webflow 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.

  • DemandMeasuredDERvalue 123

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

    Source

  • MonetisationHeuristicHEU

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

  • Growth (relative)MeasuredDERvalue 2

    Too few dated launches to measure momentum (2 in the last 90 days, 1 in the 90 before).

Existing products

All Webflow products

The most notable profiled products mentioning Webflow (up to 8). 3 indexed in total.

mcp

MCP serverby webflow.comSRC

142 GitHub starspushed 3d agoMIT

Hydori

MCP serverby hydori.ioSRC

push date unknownlicence unknown

Smootify

MCP serverby smootify.ioSRC

push date unknownlicence unknown

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
3DER
With a full profile
4DER
Launches, last 90 days
2 vs 1 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Webflow server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 123 public GitHub issues contain the phrase "Webflow mcp" (checked 2026-11-21); that is the 12th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
  • Webflow is not primarily a paid business product. This is a rule of thumb, not revenue data.
  • Too few dated launches to measure momentum (2 in the last 90 days, 1 in the 90 before).

Assumptions

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

  • Mentions of "Webflow mcp" in GitHub issues reflect developers wanting Webflow 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=%22Webflow%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 123 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 Webflow 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 .