Agent skillby nanocoaiHEU
Better agent tooling for Telegram
Integration gap · Measured demandOverall 55.8 / 100 DERConfidence Medium DERCalculated
5,119 public GitHub issues mention "Telegram mcp" (checked 2026-11-21) SRC, while 200 indexed products mention Telegram DER. On the six weighted components it scores 55.8 of 100, confidence Medium, as of 2026-11-21.
Score breakdown
Contribution = weight × component score. The contributions add up to the overall score.
| Component | Weight | Score | Score (0–100) | Contribution | Kind |
|---|---|---|---|---|---|
| Demand | 0.25 | 90.0 | 0.25 × 90.0 = 22.50 | Measured | |
| Competition gap | 0.20 | 7.0 | 0.20 × 7.0 = 1.40 | Measured | |
| Monetisation | 0.20 | 35.0 | 0.20 × 35.0 = 7.00 | Heuristic | |
| Growth (relative) | 0.15 | 60.0 | 0.15 × 60.0 = 9.00 | Measured | |
| Feasibility | 0.10 | 80.0 | 0.10 × 80.0 = 8.00 | Heuristic | |
| Distribution | 0.10 | 79.0 | 0.10 × 79.0 = 7.90 | Measured | |
| Overall | 1.00 | 55.80 → 55.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 Telegram 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 Telegram. Only some of the existing tools are both documented and actively maintained.DER
- Target users
- Developers and individuals who use TelegramHEU
- 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
- Telegram (integration)
Evidence for
4 row(s) from opportunity_evidence.
DemandMeasuredDERvalue 5,119
5119 public GitHub issues contain the phrase "Telegram mcp" (checked 2026-11-21); that is the 90th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
Growth (relative)MeasuredDERvalue 130
130 products launched in the last 90 days versus 33 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
FeasibilityHeuristicHEU
Telegram has a public API (documentation linked).
DistributionMeasuredDERvalue 37
37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.
Evidence against
2 row(s) from opportunity_evidence.
Competition gapMeasuredDERvalue 120
200 indexed products mention Telegram; 120 of them have a complete record and a repository pushed in the last 180 days.
MonetisationHeuristicHEU
Telegram is not primarily a paid business product. This is a rule of thumb, not revenue data.
Existing products
All Telegram productsThe most notable profiled products mentioning Telegram (up to 8). 200 indexed in total.
IDE extensionby unchaseSRC
MCP serverby sansan0HEU
Agent projectby enescingozHEU
MCP serverby BuilderIOSRC
Agent projectby NanmiCoderHEU
Agent projectby sandbox-quantumHEU
MCP serverby lemma-workHEU
Where it could be distributed
All platforms37 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
- 200DER
- With a full profile
- 8+DER
- Launches, last 90 days
- 130 vs 33 in the 90 beforeSRC
- Demand measured
- SRC
- Segment calculated
- Score calculated
Risks and counterarguments
- The vendor may ship (or already ships) an official Telegram server, which usually becomes the default.
- Issue mentions measure developer discussion, not willingness to pay.
- 200 indexed products mention Telegram; 120 of them have a complete record and a repository pushed in the last 180 days.
- Telegram is not primarily a paid business product. This is a rule of thumb, not revenue data.
Assumptions
What has to be true for the score to mean anything.
- Mentions of "Telegram mcp" in GitHub issues reflect developers wanting Telegram 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
- Run the demand query on GitHub: https://github.com/search?q=%22Telegram%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 5,119 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
- Check the supply on the Telegram page and search the official MCP Registry and the vendor's own app directory for an official server.
- Download the record with all evidence: /api/dataset/opportunities.json.
Page data last updated .