AdminHub for Telegram

tools.adminhubPublished by adminhub.toolsOfficial publisherv1.2.0Updated Oct 30, 2026

Run a Telegram channel from your AI agent. Posts go out through your own bot, not your account.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an AI agent run a Telegram channel, publishing posts through your own bot rather than your personal account.

What you can do
  • Publish posts to a Telegram channel from the assistant, sent through a bot you control rather than your own account.
  • No tool list is published, so the exact operations (such as scheduling, editing or reading channel content) cannot be confirmed from the available information.
When to use it
Consider it when you want an assistant to draft and publish content to a Telegram channel you administer, and you prefer bot-based posting over acting as your personal account.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth authentication is required. A Telegram channel and a bot set up for that channel are implied by the description but not documented here.
Before you install
OAuth grants the server access to act on your behalf; review the scopes before authorizing. Posts are published publicly to a channel and go out through your bot, so mistakes are visible to subscribers. No tool list or documentation is provided, so what it can read or change is unverified.

Installation

In SourceWeft

  1. Open AdminHub for Telegram in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/tools.adminhub%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "adminhub-for-telegram": {
      "type": "http",
      "url": "https://mcp.adminhub.tools/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.0LatestOct 30, 2026
  2. v1.1.0Sep 16, 2026

Score

60% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.