MCP Hub — Telegram Access
MCP Hub is a MCP server that connects your AI assistant to Telegram to browse chats and summarize messages.
About
MCP Hub is a Model Context Protocol server that connects your AI coding assistant to Telegram so you can browse chats, pull message history, and get summaries inside the agent loop. developers who run communities, beta groups, or support on Telegram often copy-paste context manually; this server exposes that channel as structured tools over MCP instead of a separate client. It targets the grow phase—especially support and lifecycle—when you need to stay responsive without tab-switching. The hosted remote uses streamable HTTP at the church.ai MCP endpoint, which fits agents that already register remote MCP servers. It is a communication integration, not a full inbox product: pairing, scopes, and Telegram account setup still sit outside the catalog entry. Use it when Telegram is a primary user touchpoint and you want Claude Code or similar agents to reason over recent threads before you reply or update docs.
- Streamable HTTP remote at mcp.ai.church for hosted MCP access
- Browse Telegram chats from the agent context
- Read and summarize messages for faster triage
- Bridges Telegram to MCP-compatible assistants (Claude Code, Cursor, Codex)
- Version 0.2.0 church.ai.mcp/mcp-hub server manifest
MCP Hub — Telegram Access by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http mcp-hub https://mcp.ai.church/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Let Claude or Cursor read Telegram chats and summarize threads without leaving the agent.
Who is it for?
Best when you run product or support communities on Telegram and already use MCP-capable agents.
Skip if: Skip if you need CRM-style ticketing, SLA workflows, or multi-channel support without Telegram.
What you get
Your agent can list chats and summarize messages over MCP so you draft responses and updates from one workspace.
- Agent-callable access to Telegram chat listing and message reads
- Summarized message context usable in support or content drafts
By the numbers
- Server version 0.2.0
- 1 streamable-http remote endpoint
- Protocol schema 2025-12-11
Recommended MCP Servers
A2atlassianJira & Confluence for AI agents.
Abm McpAccount-based marketing for AI agents.1
ACA Automated Client AcquisitionGenerate on-brand content, manage leads, and run outreach across 6 channels from your AI agent.
Activitypub McpRead-only-by-default MCP server: let LLMs explore the Fediverse — Mastodon, Misskey, Pleroma.17
Adaptive Cards McpGenerate, validate, and optimize Adaptive Cards for Teams, Outlook, and Copilot.31Adbloop Meta AdsSafe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.How it compares
Telegram MCP bridge, not a standalone chatbot or CRM skill.
FAQ
Who is church.ai.mcp/mcp-hub for?
and small-team developers who use Telegram for users or community and want Claude Code, Cursor, or Codex to read and summarize those chats via MCP.
When should I use MCP Hub?
Use it during grow and support work when you need quick thread summaries, chat browsing, or context before replying or writing lifecycle updates.
How do I add MCP Hub to my agent?
Register the remote MCP server URL https://mcp.ai.church/mcp (streamable-http) in your agent's MCP config per church.ai docs, then authorize Telegram access as required by the hub.