agentmods.dev

telegram-channel

telegram-channel is an MCP server for Claude Code from eqba1/telegram-bot-mcp. Its token cost is not measured, scanned A, original, MIT.

A local connector that lets the coding agent work with a Telegram channel through a Python server.

In plain words
What is it for?
Use it when a project needs the agent to interact with a Telegram channel through the configured server.
Why use it?
It provides a defined way to connect the agent to Telegram channel operations, instead of requiring a custom integration.

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 telegram-channel plugin — 1 skill, 1 MCP server shipped together

not rated 0repo 18d ago A scan tokens not measured original MIT

Good fit Use it when a project needs the agent to interact with a Telegram channel through the configured server.

Compare 6 mcp servers from other repositories ↓
View source ↗ eqba1/telegram-bot-mcp
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 eqba1/telegram-bot-mcp
Claude Code
/plugin install telegram-channel

Made for: Claude Code.

Or install telegram-channel, the plugin that ships this one along with the rest of its 1 skill, 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-channel

README.md
[![agentmods](https://agentmods.dev/badge/mcp/eqba1/telegram-bot-mcp/telegram-channel.svg)](https://agentmods.dev/mcp/eqba1/telegram-bot-mcp/telegram-channel)
Your own site
<a href="https://agentmods.dev/mcp/eqba1/telegram-bot-mcp/telegram-channel"><img src="https://agentmods.dev/badge/mcp/eqba1/telegram-bot-mcp/telegram-channel.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 original No closer match found in the catalogue.
Security

Grade A, and why

telegram-channel 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 6d 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.

plugin/.mcp.json · 8 lines

What it actually says

{
  "telegram-channel": {
    "command": "python3",
    "args": [
      "${CLAUDE_PLUGIN_ROOT}/server/telegram_mcp_server.py"
    ]
  }
}
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. 6d ago First seen · 8 lines scan A d9105b813786

Subscribe to this mod's changes

telegram-channel is an MCP server published in the GitHub repository eqba1/telegram-bot-mcp (0 stars, last pushed 18d ago), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

mcpmcp-toolstelegram
Related

Other mcp servers, from other repositories

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

playwright

Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.

langbot-app/LangBot · not measured

redmine-mcp-server

MCP server that lets AI assistants manage Redmine issues, projects, wikis, and time tracking. Runs locally from the redmine-mcp-server Python package. Needs 12 environment variables to run.

jztan/redmine-mcp-server · not measured

clio-compression

MCP server "clio-compression" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server compression.

iowarp/clio-kit · not measured

clio-paraview

MCP server "clio-paraview" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server paraview.

iowarp/clio-kit · not measured

clio-scientific-catalog

MCP server "clio-scientific-catalog" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server scientific-catalog.

iowarp/clio-kit · not measured