Skip to main content
Glama
Sign In

Telegram MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Telegram MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/telegram-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation4/5

The tools mostly have distinct roles within an enforced workflow: query_contexts for metadata/planning, query_data for data retrieval, execute_action for mutations, and prompts_menu for prompt catalog browsing. The main ambiguity is between query_contexts and query_data because both use 'query' and are adjacent steps, but the descriptions clarify their different stages.

Naming Consistency4/5

Three tools follow a clear verb_noun pattern: execute_action, query_contexts, and query_data. prompts_menu is a minor deviation from that pattern, but it is still readable and does not significantly harm predictability.

Tool Count5/5

Four tools is well-scoped for a staged Telegram workflow: one discovery/helper tool, one data query tool, one action execution tool, and one prompt catalog tool. Each tool appears to earn its place without excessive surface area.

Completeness4/5

The surface covers workspace/account discovery, action schema inspection, action execution, data querying, and prompt browsing, which are the key workflow operations. Some direct convenience operations may be absent, but the generic action and query mechanisms likely allow agents to work around those gaps.

Available Tools

4 tools
execute_actionTelegram Execute ActionA
Destructive
Inspect

Execute Telegram action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuTelegram PromptsA
Read-only
Inspect

Browse the Telegram prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsTelegram Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Telegram data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataTelegram Data QueryB
Read-only
Inspect

Query Telegram data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • telegram-account-orchestrator

      soulknight666
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for self-hosted Telegram multi-account management, enabling encrypted session storage, health checks, batch operations, device-session management, and automation through AI agents.
      23
      MIT

    • Postun

      AiReformator
      A
      license
      Not graded
      quality
      B
      maintenance
      An open-source, read-only MCP server that connects your own Telegram account to ChatGPT, Claude and Claude Code via OAuth, enabling access to chats, message history, search, public channels and files with per-client scopes and revocable grants.
      Apache 2.0

    • tg-max-mcp

      minchiki
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT, Claude, Cursor, and other MCP clients to read and send messages, manage chats, groups, media, polls, and profiles in a user's personal Telegram and MAX accounts via a self-hosted server.
      1
      MIT

    • MCP-Telegram

      mcp-telegram
      A
      license
      B
      quality
      B
      maintenance
      An MCP (Model Context Protocol) server that connects AI assistants like Claude to Telegram via the MTProto protocol. Unlike bots, this runs as a userbot -- it operates under your personal Telegram account using GramJS, giving full access to your chats, contacts, and message history.
      169
      2,134 npm
      64
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources