tgfmcp
tgfmcp is an open-source Telegram stdio MCP server built on top of , , and .
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
Abrircommander@modelcontextprotocol/sdkIt lets MCP-compatible clients interact with the Telegram Bot API through Telegraf and optionally subscribe to incoming Telegram events through an MCP notification channel.
telegraf directly for polling and Bot API operations.tgfmcp configure.~/.tgfmcp/attachments/.24+Use it without installing globally:
npx tgfmcp mcp
Or with Bun:
bunx tgfmcp mcp
If you prefer a global install:
npm install -g tgfmcp
For local development:
npm install
npm run build
npm run dev -- mcp
tgfmcp configure
This writes:
~/.tgfmcp/config.json
npx tgfmcp mcp
npx tgfmcp mcp --channels
The server uses stdio, so it is meant to be launched by an MCP client or wrapper rather than browsed directly in a terminal.
npx tgfmcp mcp
bunx tgfmcp mcp
Starts the stdio MCP server for the configured Telegram bot.
npx tgfmcp configure
Then opens an interactive configure UI (Ink) to manage:
Bot tokenAllowed usersAllowed chatsAllowlist items are toggled from menu screens (select an entry to toggle it, then choose Back).
For enrolling users/chats, configure can generate a short code per screen and watch incoming Telegram updates. Send the code from the target user/chat and the matching ID is auto-added to allowlist.
Everything is persisted to:
~/.tgfmcp/config.json
The server currently exposes these tools:
telegram_get_metelegram_get_statustelegram_get_chattelegram_get_chat_administratorstelegram_lookup_chattelegram_send_messagetelegram_send_media_from_base64telegram_send_media_from_pathtelegram_reply_to_messagetelegram_react_to_messagetelegram_edit_messagetelegram_delete_messagetelegram_forward_messagetelegram_send_typingWhen started with --channels, the server:
hooman/channelhooman/user with path meta.userhooman/session with path meta.sessionhooman/thread with path meta.threadhooman/channel/permission for remote daemon approvalsnotifications/hooman/channel for incoming Telegram message eventsIf allowlist entries are configured, notifications/hooman/channel events are emitted only when either:
meta.session (chat ID) is in allowlist.chats, ormeta.user (sender user ID) is in allowlist.usersWhen no allowlist is configured (or both arrays are empty), all inbound channel events are emitted.
Each notification includes:
content: a JSON-encoded event payloadmeta.source: always telegrammeta.user: the sender identity seed for the incoming messagemeta.session: the chat identity seed for the incoming messagemeta.thread: the Telegram message ID for the incoming messageThe JSON-decoded content payload includes:
sourceselfmessagetextIf an incoming message contains downloadable media, the file is downloaded and included as a local attachment path in the event payload. Files are stored under ~/.tgfmcp/attachments/.
When Hooman sends notifications/hooman/channel/permission_request, tgfmcp posts the request back into the originating Telegram chat with inline approval buttons from params.options. Button selections are relayed back over notifications/hooman/channel/permission.
Approvals are handled through inline buttons rendered from the permission request options.
tgfmcp stores local state under ~/.tgfmcp/:
config.json for bot token and allowlistattachments/ for downloaded incoming media attachmentschatId and messageId inputs.MIT. See LICENSE.
tgfmcp is an open-source Telegram stdio MCP server built on top of telegraf, commander, and @modelcontextprotocol/sdk.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Tgfmcp se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. tgfmcp is an open-source Telegram stdio MCP server built on top of telegraf, commander, and @modelcontextprotocol/sdk.