agentmods.dev

telegram

telegram is an MCP server for Claude Code from shakhruz/mila-telegram. Its token cost is not measured, scanned A, a copy of whatsapp, Apache-2.0.

A connection for working with Telegram, a messaging app. The provided information only identifies the Telegram server and how it is launched, not what actions it supports.

In plain words
What is it for?
Use it wherever a project needs the configured Telegram server; check its available commands before relying on a specific task.
Why use it?
It gives a coding agent a configured way to reach the Telegram integration, but the available information is too limited to say which Telegram tasks it can perform.

MCP server for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: listed in a Claude config.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the mila-telegram plugin — 2 skills, 1 MCP server shipped together

not rated 1repo 12d ago A scan tokens not measured copy · 86% Apache-2.0

Good fit Use it wherever a project needs the configured Telegram server; check its available commands before relying on a specific task.

Compare 6 mcp servers from other repositories ↓
View source ↗ shakhruz/mila-telegram
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add shakhruz/mila-telegram
Claude Code
/plugin install mila-telegram

Made for: Claude Code.

Or install mila-telegram, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for telegram

README.md
[![agentmods](https://agentmods.dev/badge/mcp/shakhruz/mila-telegram/telegram.svg)](https://agentmods.dev/mcp/shakhruz/mila-telegram/telegram)
Your own site
<a href="https://agentmods.dev/mcp/shakhruz/mila-telegram/telegram"><img src="https://agentmods.dev/badge/mcp/shakhruz/mila-telegram/telegram.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

telegram scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to whatsapp — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.mcp.json · 13 lines

What it actually says

{
  "telegram": {
    "command": "bun",
    "args": [
      "run",
      "--cwd",
      "${CLAUDE_PLUGIN_ROOT}",
      "--shell=bun",
      "--silent",
      "start"
    ]
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 13 lines scan A 382d2867a44a

Subscribe to this mod's changes

telegram is an MCP server published in the GitHub repository shakhruz/mila-telegram (1 stars, last pushed 12d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 86% identical to whatsapp, differing in 2 lines, and is treated as a copy.

Claude Codeclaudemcptelegramtelegram-bot
Related

Other mcp servers, from other repositories

mcp-telegram-claudecode

MCP server for Telegram integration with Claude Code - Send and receive messages via Telegram. Runs locally from the mcp-telegram-claudecode npm package.

EthanSky2986/mcp-telegram-claudecode · not measured

github

Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.

langbot-app/LangBot · not measured

sequential-thinking

Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.

langbot-app/LangBot · not measured

codegraph

MCP server "codegraph" as configured in sirquy/bestie. Launched with codegraph serve --mcp.

sirquy/bestie · not measured

shadcn

Add components to your apps. Runs locally from the shadcn npm package.

langbot-app/LangBot · not measured

telegram-account-orchestrator

MCP server "telegram-account-orchestrator" as configured in soulknight666/telegram-account-orchestrator. Runs locally from the telegram-account-orchestrator Python package.

soulknight666/telegram-account-orchestrator · not measured