Telegram MCP Server

Created By
bmwdrocha year ago
Overview

What is Telegram MCP Server?

Telegram MCP Server is a server designed for integrating AI agents with Telegram, allowing for synchronous messaging between users and AI agents.

How to use Telegram MCP Server?

To use the Telegram MCP Server, create a Telegram bot via @BotFather to obtain a token, set up your chat ID, and run the server using Docker with the appropriate configurations.

Key features of Telegram MCP Server?

  • Integration with AI agents via the MCP protocol
  • Sending messages to Telegram users
  • Waiting for user responses with customizable timeouts
  • Synchronous operation where the agent waits for user replies
  • Secure token storage through environment variables
  • Ready-to-use Docker container for easy deployment

Use cases of Telegram MCP Server?

  1. Integrating AI agents in services that support MCP (like Cursor, WindSurf, Anthropic).
  2. Sending and receiving messages in real-time between users and AI agents.
  3. Building interactive applications that require user input through Telegram.

FAQ from Telegram MCP Server?

  • Can I use this server with any AI agent?

Yes! The server is designed to work with any AI agent that supports the MCP protocol.

  • Is there a cost to use the Telegram MCP Server?

No, the server is open-source and free to use.

  • How do I deploy the server?

You can deploy the server using Docker by following the quick start guide provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bmwdroch
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago