TeleBoost
Telegram CRM: manage contacts, conversations, tickets, campaigns and analytics.
likely compatible
OAuth with discovery metadata and Dynamic Client Registration; use OAuth 2.0 → Dynamic discovery.
Rule R2c · what this means · Not tested in Copilot Studio.
| Registry name | app.teleboost/teleboost |
| Endpoint used for verdict | https://mcp.teleboost.app/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | OAuth 2.0 – Dynamic discovery |
| Last endpoint check | 2026-10-20T18:10:12Z · HTTP 401 |
| Website | https://teleboost.app/telegram-mcp |
| Version | 1.0.0 |
| Registry updated | 2026-08-19 |
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-20.