Telegram MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.3.4Updated Nov 7, 2026

Read chats and members; send, edit and delete messages with a bot in Telegram.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Hosted Telegram bot server that lets an assistant read chats and members and send, edit or delete messages via the Bot API.

What you can do
  • Inspect the bot itself and the chats it belongs to, including type, title, description and permissions
  • Count members and look up a single member's status and rights
  • List the administrators of a group or channel
  • Read pending messages and events queued for the bot, with offset-based acknowledgement
  • Send, edit and delete messages as the bot
  • Check monthly usage, request a feature, and upgrade or cancel a paid plan
When to use it
Useful when you want an assistant to monitor or answer messages arriving at a Telegram bot, report channel or group membership and admins, or post and manage messages in a team group or channel without writing Bot API code.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local install. Sign-in is via OAuth, and the login page asks for a Telegram bot token obtained from BotFather, which the server validates and stores per user. No API key or Authorization header goes in the client config. Network access to the hosted endpoint is required.
Before you install
The bot token is a credential entered on the provider's login page and stored server-side. Send, edit and delete act on real chats and are visible to people; deletion cannot be undone and is limited to messages the bot may delete and mostly to those under 48 hours old. Reading updates with an offset deletes older updates in Telegram irreversibly. Paid plans cost money and are billed through a Stripe checkout link; the free tier is capped at 50 calls per month.

Installation

In SourceWeft

  1. Open Telegram MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Ftelegram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "telegram-by-usefulapi": {
      "type": "http",
      "url": "https://telegram.usefulapi.io/mcp"
    }
  }
}

README

Telegram MCP by usefulapi

Use your Telegram account from Claude, Cursor, or any MCP client. Read chats, members and administrators of your bot, and send, edit and delete messages with the bot. Hosted, no local install: connect with your own credentials.

Live endpoint: https://telegram.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://telegram.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http telegram https://telegram.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "telegram": {      "url": "https://telegram.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Telegram credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/telegram/

On first connect you provide a Telegram bot token (open @BotFather in Telegram, send /newbot or /mybots, then API Token). The server validates it and stores it per user. No keys go in config files.

Tools

ToolTypeWhat it does
telegram_get_mereadGet the bot
telegram_get_chatreadGet a chat
telegram_get_chat_member_countreadCount chat members
telegram_get_chat_memberreadGet a chat member
telegram_get_chat_administratorsreadList chat administrators
telegram_get_updateswriteGet pending updates
telegram_send_messagewriteSend a message
telegram_edit_message_textwriteEdit a message
telegram_delete_messagewriteDelete a message
telegram_usage_statusmetaUsage status (free-tier meter)
telegram_request_featuremetaRequest a missing feature
telegram_upgrademetaUpgrade to Pro or Pro+
telegram_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with telegram_upgrade (it returns a Stripe Checkout link). Cancel any time with telegram_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running telegram_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/telegram/README.md at commit 4046075

Tools

9

telegram_get_me

Get the bot

Return the bot's own profile (id, name, username, group-join and inline settings). Use it to confirm the token works. Bot API: getMe.

Takes no parameters.

telegram_get_chat

Get a chat

Get the details of a chat the bot belongs to: type, title, username, description, pinned message, permissions. Bot API: getChat.

Parameterschat_idrequired

telegram_get_chat_member_count

Count chat members

Get the number of members in a chat. Bot API: getChatMemberCount.

Parameterschat_idrequired

telegram_get_chat_member

Get a chat member

Get one member of a chat: status (creator, administrator, member, restricted, left, kicked) and rights. Bot API: getChatMember.

Parameterschat_idrequireduser_idrequired

telegram_get_chat_administrators

List chat administrators

List the administrators of a group or channel (not other bots' hidden admins). Bot API: getChatAdministrators.

Parameterschat_idrequired

telegram_get_updates

Get pending updates

Read the messages and events that users sent to the bot and that wait in Telegram's queue (short poll, no wait). Without offset the same updates return again. A positive offset above an update_id, or a negative offset, deletes older updates in Telegram (this cannot be undone). allowed_updates changes the bot's saved update filter. Fails with HTTP 409 if the bot has a webhook. Bot API: getUpdates.

Parameterslimitoffsetallowed_updates

telegram_send_message

Send a message

WRITE: send a text message from the bot to a chat. The message is visible to real people and cannot be unsent except with telegram_delete_message. Bot API: sendMessage.

Parameterstextrequiredchat_idrequiredparse_modemessage_thread_idreply_to_message_iddisable_notification

telegram_edit_message_text

Edit a message

WRITE: change the text of a message that the bot sent. This replaces the old text. Bot API: editMessageText.

Parameterstextrequiredchat_idrequiredmessage_idrequiredparse_mode

telegram_delete_message

Delete a message

WRITE: delete a message. This cannot be undone. A bot can delete its own messages and incoming private-chat messages. In groups it needs the delete-messages admin right for other messages. Telegram allows deletion only for messages up to 48 hours old in most cases. Bot API: deleteMessage.

Parameterschat_idrequiredmessage_idrequired

Version history

6
  1. v1.3.4LatestNov 7, 2026
  2. v1.2.3Nov 5, 2026
  3. v1.2.2Nov 5, 2026
  4. v1.2.1Nov 4, 2026
  5. v1.2.0Nov 3, 2026
  6. v1.1.1Nov 3, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations