Telegram MCP Server

Created By
abhinavkale-deva year ago
Simple Telegram MCP server
Overview

what is Telegram MCP Server?

Telegram MCP Server is a Model Context Protocol server designed for the Telegram Bot API, enabling AI assistants to interact with Telegram using standardized tools.

how to use Telegram MCP Server?

To use the Telegram MCP Server, follow these steps:

  1. Install dependencies using npm install.
  2. Create a .env file with your Telegram Bot Token.
  3. Build the TypeScript project with npm run build.
  4. Start the server using npm start.

key features of Telegram MCP Server?

  • Supports operations like sending messages, sending photos, and deleting messages.
  • Compatible with any MCP-compatible client.
  • Built using TypeScript and the Telegram Bot API.

use cases of Telegram MCP Server?

  1. Sending automated messages to users in a Telegram chat.
  2. Sharing images or media content in Telegram conversations.
  3. Managing chat messages by deleting unwanted messages.

FAQ from Telegram MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a standardized way for AI assistants to communicate with various platforms, including Telegram.

  • Is the Telegram MCP Server free to use?

Yes! The Telegram MCP Server is open-source and free to use.

  • What programming language is used for the server?

The server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhinavkale-dev
Star
1
Language
TypeScript
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