Telegram Notification MCP Server

Created By
kstonekuana year ago
Simple MCP server to send you notifications on telegram
Overview

What is Telegram Notification MCP Server?

Telegram Notification MCP Server is a simple Model Context Protocol (MCP) server that sends notifications to Telegram when tasks are completed by Claude Code. It is built with TypeScript and deployable on Cloudflare Workers.

How to use Telegram Notification MCP Server?

To use the server, create a Telegram bot via @BotFather, obtain your bot token and chat ID, clone the repository, install dependencies, configure your environment variables, and deploy it to Cloudflare Workers.

Key features of Telegram Notification MCP Server?

  • MCP Tool: Provides a send_telegram_message tool for sending notifications.
  • Cloudflare Workers: Runs serverless with global distribution.
  • Secure: Utilizes Cloudflare secrets for credentials.
  • Dual Transport: Supports both SSE and Streamable HTTP for maximum compatibility.
  • Message Formatting: Supports Markdown and HTML formatting.

Use cases of Telegram Notification MCP Server?

  1. Sending notifications when tasks are completed.
  2. Alerting users about errors during task execution.
  3. Informing users about important milestones or user input requirements.

FAQ from Telegram Notification MCP Server?

  • How do I set up the server?

    Follow the setup instructions in the documentation, including creating a Telegram bot and configuring environment variables.

  • What programming language is used?

    The server is built using TypeScript.

  • Is it free to use?

    Yes, the server is free to use as it runs on Cloudflare Workers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kstonekuan
Star
1
Language
TypeScript
License
MIT 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)

6 hours ago