Integration coverage report
Demand (GitHub issue mentions) against supply (indexed agent products) for 111 third-party services, with the integrations no agent product covers.
Executive summary
111 third-party integrations are tracked; 7,671 product–integration mentions exist across them, and 1 integration(s) have no products at all.
Demand has been measured for 111 integrations: 419,715 GitHub issue mentions in total, checked on 2026-11-21.
Make has the highest demand-to-supply ratio: 41,232 issue mentions against 2 products (20,616 per product).
The 29 enterprise-focused integrations have a median of 24 products each, against 38 for the rest.
YouTube has the most supply (574 products); GitHub follows with 552.
Every figure above is computed from the database DER
Methodology
How this report was produced, and its limits
Generated on 2026-11-21 from the AgentSidekick database. The latest completed ingestion step finished at 2026-11-21 13:23 UTC. Tables queried: integrations, market_segments, demand_signals, product_integrations. The catalogue holds 73,820 active products, of which 9,469 meet the data-completeness bar and have a profile page.
Enterprise flag and public-API flag are curated in the integration configuration; they are judgments, not measurements.
Classification method: product type comes from the source (registry entries are MCP servers by definition) or is inferred from repository topics; categories, capabilities, integrations and industries come from keyword rules in the editable taxonomy, so they are derived, not checked by a person. Curated records were researched against the official sources listed on each record.
Known limits:
- Supply = active products whose name or description mentions the integration (keyword match on the name and its aliases). Official vendor servers and one-file wrappers count the same.
- Demand = the number of public GitHub issues and pull requests matching "<integration name>" "mcp server", from the GitHub search API. It counts developer discussion, not users or buyers, and integrations whose names are common words or shared with other projects are inflated.
- The ratio divides demand by supply (supply floored at 1). It is a sorting aid; a high ratio can mean an unmet need or a noisy name.
- Categories, capabilities and integrations are assigned by keyword rules over names and descriptions (derived). Products that do not name a capability are missed, and generic words can produce false matches.
- Only 1 daily metrics snapshot(s) exist in product_metrics, so growth is measured from launch counts, not from changes in stars or downloads.
Note. Claim labels: source = stated by the publisher or registry; curated = checked by us against cited sources; derived = computed by a documented rule; heuristic = a rule of thumb with no measurement behind it. Full method: methodology.
Demand against supply
Sorting by issue mentions per product puts the least-served integrations first. Make leads with 20,616 mentions per product. The top of this list deserves the most scepticism: the biggest raw demand counts (GitHub 153,165, Make 41,232, Docker 22,083) include issues that mention the word for reasons unrelated to the product. Use the linked search for each row to see what the matches actually are.
Integrations by demand per productDER
Issue mentions link to the GitHub search that produced them.
Where supply is deepest
Supply is concentrated. The five most-covered integrations account for 2,190 of 7,671 product mentions (28.5%). Heavy supply usually means a free, developer-facing API that is easy to wrap; it does not mean those integrations are well served, since many entries are thin wrappers that duplicate each other.
Supply is still growing quickly: across all tracked integrations, 4,075 product mentions come from products launched in the last 90 days, against 1,391 in the 90 days before. Between the deep end and the empty end, 6 integrations have between one and four products, which is the zone where one well-maintained, documented tool can become the default choice.
Integrations with the most productsDER
| Integration | Group | Products | New 90d | Prev 90d | Label | Issue mentions |
|---|---|---|---|---|---|---|
| YouTube | media | 574 | 409 | 98 | Crowded, outpacing the catalogue | 1,435 (external) |
| GitHub | source-control | 552 | 245 | 98 | Crowded, slowing | 153,165 (external) |
| social | 420 | 287 | 78 | Crowded | 1,377 (external) | |
| Solana | blockchain | 357 | 206 | 86 | Crowded, slowing | 770 (external) |
| PostgreSQL | database | 287 | 140 | 61 | Crowded, slowing | 3,389 (external) |
| communication | 285 | 200 | 48 | Crowded, outpacing the catalogue | 2,035 (external) | |
| Android | mobile | 228 | 136 | 32 | Crowded, outpacing the catalogue | 3,102 (external) |
| Shopify | commerce | 228 | 163 | 38 | Crowded, outpacing the catalogue | 902 (external) |
| Telegram | communication | 200 | 130 | 33 | Crowded | 5,119 (external) |
| social | 196 | 112 | 36 | Crowded | 1,055 (external) | |
| Stripe | payments | 189 | 82 | 75 | Crowded, slowing | 1,889 (external) |
| AWS | cloud | 162 | 43 | 35 | Crowded, slowing | 6,561 (external) |
| WordPress | media | 155 | 112 | 19 | Crowded, outpacing the catalogue | 1,828 (external) |
| Google Ads | marketing | 153 | 115 | 18 | Crowded, outpacing the catalogue | 502 (external) |
| Gmail | communication | 126 | 63 | 25 | Crowded, slowing | 4,818 (external) |
By group
Grouping integrations by what they are (CRM, database, communication and so on) smooths out noise from individual names. Groups at the top of this table have the most demand per indexed product. Automation leads with 755 mentions per product across 3 integration(s).
Raw GitHub issue mentions, top 15 integrationsSRC
Unit: issues. Top 15 shown.
Show the data as a table
| issues | |
|---|---|
| GitHub | 153,165 |
| Make | 41,232 |
| Docker | 22,083 |
| Playwright | 21,121 |
| OpenAPI | 12,615 |
| SQLite | 9,661 |
| Azure | 8,824 |
| Slack | 7,732 |
| Cloudflare | 6,940 |
| AWS | 6,561 |
| Figma | 5,543 |
| Telegram | 5,119 |
| Supabase | 5,092 |
| Notion | 5,037 |
| Gmail | 4,818 |
The raw counts above are the input to every ratio in this report. They are dominated by a handful of names: the top three account for 51.6% of all 419,715 mentions. Group totals are therefore pulled toward whichever group contains those names, and a single noisy name can make a whole group look under-served.
Integration groups by demand per productDER
| Group | Integrations | Products | Issue mentions | Mentions per product |
|---|---|---|---|---|
| Automation | 3 | 59 | 44,562 | 755 |
| Source control | 3 | 608 | 156,279 | 257 |
| Testing | 3 | 99 | 22,096 | 223 |
| Devops | 3 | 203 | 28,251 | 139 |
| Monitoring | 4 | 64 | 6,505 | 102 |
| Iot | 1 | 18 | 1,733 | 96 |
| Storage | 4 | 82 | 6,425 | 78 |
| Project management | 6 | 120 | 9,353 | 78 |
| Vector db | 4 | 30 | 2,305 | 77 |
| Api | 4 | 263 | 17,553 | 67 |
| Design | 3 | 100 | 6,015 | 60 |
| Cloud | 6 | 466 | 26,862 | 58 |
| Game 3d | 4 | 129 | 6,967 | 54 |
| Database | 10 | 612 | 25,369 | 41 |
| Productivity | 9 | 415 | 13,982 | 34 |
| Communication | 9 | 916 | 24,719 | 27 |
| Support | 2 | 20 | 482 | 24 |
| Data warehouse | 4 | 92 | 1,669 | 18 |
| Crm | 2 | 73 | 1,093 | 15 |
| Enterprise | 3 | 117 | 1,637 | 14 |
| Mobile | 2 | 301 | 3,192 | 11 |
| Payments | 2 | 210 | 2,044 | 10 |
| Analytics | 3 | 127 | 792 | 6 |
| Media | 4 | 790 | 3,831 | 5 |
| Accounting | 2 | 79 | 343 | 4 |
Enterprise integrations
29 integrations are flagged as sold mainly to businesses. Their median supply is 24 products against 38 for consumer and developer services, and their median demand is 558 issue mentions against 920. Enterprise systems tend to need paid accounts and admin approval to build against, which keeps hobby supply low.
A public API is the main precondition for supply. The 105 integrations recorded with a public API have a median of 29 products; the 6 recorded without one have a median of 61. Where there is no public API, building an agent tool usually needs a partner agreement, which no amount of developer demand can substitute for.
Enterprise integrationsCUR
Enterprise and public-API flags are curated; counts are derived.
Integrations with no products
1 tracked integration(s) are not mentioned by any indexed product. Either no agent tool exists for them, or existing tools describe themselves without naming the service.
- Box (storage): 4,649 issue mentions
Recommendations
Editorial: the judgement of AgentSidekick, drawn from the figures above. Not a measurement, not investment advice.
- Editorial
before building for Make (20,616 mentions per product), open its issue search and check that the matches are about the product, not the word.
- Editorial
the 1 integration(s) with no products are the cheapest gaps to verify: search the vendor's own docs for an official server first.
- Editorial
enterprise integrations have a median of 24 products; a maintained, documented server there faces less competition than in the 574-product YouTube segment.
Sources
- GitHub issue search counts: docs.github.com (external)checked
- Official MCP Registry: registry.modelcontextprotocol.io (external)checked
- GitHub topic search: docs.github.com (external)checked
- AgentSidekick methodology: agentsidekick.dev (external)checked
Data behind this report
- Integrations and detection aliases: /api/dataset/integrations.jsonJSON, regenerated each build
- Per-segment counts and launch momentum: /api/dataset/segments.jsonJSON, regenerated each build
- Scored opportunities with evidence: /api/dataset/opportunities.jsonJSON, regenerated each build
Cite this report
Integration coverage report. AgentSidekick, 2026-11-21. https://www.agentsidekick.dev/reports/integration-coverage-report/
Figures change when the database is refreshed; cite the date shown.