AdminHub for Telegram
Run a Telegram channel from your AI agent. Posts go out through your own bot, not your account.
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 | tools.adminhub/telegram |
| Endpoint used for verdict | https://backend-git-production-cb93.up.railway.app/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | OAuth 2.0 – Dynamic discovery |
| Last endpoint check | 2026-10-20T18:18:31Z · HTTP 401 |
| GitHub | siteboss777-lgtm/telegram-admin-hub |
| Website | https://adminhub.tools/mcp/ |
| Version | 1.1.0 |
| Registry updated | 2026-09-08 |
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.