MCP Hub — Telegram Access
Let Claude or Cursor read Telegram chats and summarize threads without leaving the agent.
Overview
MCP Hub is a MCP server for the Grow phase that connects your AI assistant to Telegram to browse chats and summarize messages.
What is this MCP server?
- 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
- Server version 0.2.0
- 1 streamable-http remote endpoint
- Protocol schema 2025-12-11
What problem does it solve?
Builders lose time copying Telegram threads into the agent when they need summaries or context for support replies.
Who is it for?
Indie builders who run product or support communities on Telegram and already use MCP-capable agents.
Skip if: Teams that need CRM-style ticketing, SLA workflows, or multi-channel support without Telegram.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Community and user conversations live in Telegram for many indie products; grow-phase support and lifecycle work benefits from agent-readable messaging. Support subphase covers async channels where builders answer users and triage inbound messages.
How it compares
Telegram MCP bridge, not a standalone chatbot or CRM skill.
Common Questions / FAQ
Who is church.ai.mcp/mcp-hub for?
Solo and small-team builders 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.