telegram

Telegram: FASTEST real time Telegram API. Retrieve channel's info and messages in milliseconds..

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
70%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~125Tokens (tool definitions)
~458 BTypical response size
Minimal attention impact (0.10% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "telegram": {
      "url": "https://mcp.jojapi.com/telegram"
    }
  }
}

Remote endpoints

https://mcp.jojapi.com/telegramstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_channel_info(channel)

Telegram channel info Billing per call: 1 Credits.

Input Schema

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "example": "telegram"
    }
  },
  "additionalProperties": false
}
🟢get_channel_message(channel, limit, max_id)

Telegram channel messages Billing per call: 1 Credits.

Input Schema

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "example": "telegram"
    },
    "limit": {
      "type": "string",
      "example": "5"
    },
    "max_id": {
      "type": "string",
      "example": "99999"
    }
  },
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools