MCP.Market

Dynamic Telegram Bot API MCP server

by patricktobias86·io.github.patricktobias86/dynamic-telegram-bot-api-mcp·v10.3.3
No reviews yet

A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars337 downloads/wk

Reviews

Write one

Nobody has reviewed Dynamic Telegram Bot API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dynamic Telegram Bot API tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • telegram_call_methodwrite action

    Validate and execute any current Telegram Bot API method. Destructive methods require confirm=true. Local files and base64 upload descriptors are converted to multipart uploads.

  • telegram_get_method

    Return the complete current schema for one Telegram Bot API method.

  • telegram_get_type

    Return the complete current definition of a Telegram Bot API object or union type.

  • telegram_refresh_schema

    Fetch and atomically install the latest schema from the official Telegram Bot API documentation.

  • telegram_search_methods

    Fuzzy-search every Telegram Bot API method by name, description, category, or parameter name.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan40 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dynamic Telegram Bot API compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,243 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
337
more than 82% of 12,306 servers with a package

What its tools let an agent do: 4 read · 1 change

Install Dynamic Telegram Bot API in Claude Code, Cursor or VS Code

Runs npx -y dynamic-telegram-bot-api-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add dynamic-telegram-bot-api-mcp -- npx -y dynamic-telegram-bot-api-mcp
Add to Cursor

What the publisher says

From the Dynamic Telegram Bot API repository's README, as published. We do not edit it. Read it on GitHub

Dynamic Telegram Bot API MCP Server

A production-oriented Model Context Protocol server that exposes the complete Telegram Bot API through five stable tools. It parses Telegram's official documentation into a normalized local catalog, so new Bot API methods and objects become available after a schema refresh without source-code changes.

The checked-in catalog targets the Telegram Bot API version recorded in data/telegram-bot-api.json and contains every method and type published in the official documentation.

MCP tools

There is deliberately no generated tool per Bot API method. The catalog and generic call tool are the API surface.

Requirements and installation

  • Node.js 20.18.1 or later
  • A bot token from @BotFather for API calls (catalog tools work without one)

Install from npm

Run the published npm package directly with npx—no repository checkout or build is required:

Create a .env in each project or repository with that project's bot token:

TELEGRAM_BOT_TOKEN=YOUR_PROJECT_BOT_TOKEN
TELEGRAM_METHOD_ALLOWLIST=get*,sendMessage,sendPhoto

Configure the MCP server once, without a shared token or hard-coded working directory:

{
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": ["-y", "dynamic-telegram-bot-api-mcp"]
    }
  }
}

For Codex, the equivalent ~/.codex/config.toml entry is:

[mcp_servers.telegram]
command = "npx"
args = ["-y", "dynamic-telegram-bot-api-mcp"]

Alternatively, install it globally with npm install -g dynamic-telegram-bot-api-mcp and use "command": "telegram-bot-api-mcp" in the configuration above, omitting args.

Registry name: io.github.patricktobias86/dynamic-telegram-bot-api-mcp.

Install from GitHub

Clone and build the GitHub repository:

git clone https://github.com/PrimeUpYourLife/dynamic-telegram-bot-api-mcp.git
cd dynamic-telegram-bot-api-mcp
npm ci
npm run build

Then configure an MCP client to start the built stdio server. Use an absolute repository path:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dynamic Telegram Bot API: common questions

Is Dynamic Telegram Bot API MCP server safe?
Mostly: it is graded B (80/100). Read the Dynamic Telegram Bot API safety report
How do I install Dynamic Telegram Bot API?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dynamic Telegram Bot API need an API key?
Yes. The registry entry asks for TELEGRAM_BOT_TOKEN.
Is Dynamic Telegram Bot API maintained?
The last commit was 22 days ago (2026-10-14). The latest release is v10.3.3.
How does Dynamic Telegram Bot API compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.