No install? Use cloud.anythingmcp.com directly.
Sign in, install the Telegram Bot in one click, paste the credentials, mint an MCP API key — done. No Docker, no git clone, no local server to run.
TL;DR
Send Telegram messages, photos, documents, audio, location and polls from any AI agent via the Telegram Bot API. 14 tools, bot-token auth. Outbound + lightweight read of recent updates (no long-polling).
💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → Telegram Bot klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein
git clone, kein lokaler Server.
Telegram Bot + Gemini
Send Telegram messages, photos, documents, audio, location and polls from any AI agent via the Telegram Bot API. 14 tools, bot-token auth. Outbound + lightweight read of recent updates (no long-polling).
Voraussetzungen
Die vollständige Setup-Anleitung ist in den Connector eingebaut (im Store sichtbar, wenn du den Connector auswählst). Benötigte Umgebungsvariablen für diesen Connector:
TELEGRAM_BOT_TOKEN
Schritt 1 — Zugangsdaten holen
telegram.org/bots/api).
Setup:
- In Telegram, open chat with @BotFather →
/newbot→ pick a display name and a username ending inbot. - BotFather replies with an HTTP API token like
123456789:ABCDEFghijklmnopqrstuvwxyz. Treat as a secret — anyone with it can send as your bot. - Set
TELEGRAM_BOT_TOKENto the full token.
Authentication model (Telegram-specific): the bot token goes in the URL path, NOT in a header. The base URL is https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN} and every endpoint is appended as /methodName. The adapter substitutes the token via the {{TELEGRAM_BOT_TOKEN}} env-var template in baseUrl.
…(continued in the in-app connector instructions)
Schritt 2 — Adapter installieren
git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d
Schritt 3 — Connector in Gemini hinzufügen
Gemini CLI liest MCP-Server aus ~/.gemini/settings.json (oder %APPDATA%\gemini\settings.json unter Windows). Hinzufügen:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MCP_API_KEY" }
}
}
}
- Hole deinen MCP API Key aus AnythingMCP → Profil → MCP API Keys → Neuer Key.
- Speichern und
geminineu starten. /mcpin Gemini CLI ausführen —Telegram Botsollte als verfügbar gelistet sein.- Vertex AI Studio:
https://cloud.anythingmcp.com/mcpimtools-Array der Anfrage mit demselben Bearer-Header übergeben.
Verfügbare Tools
| Tool | What it does |
|---|---|
telegram_bot_get_me | Return the bot's own user info: id, username, first_name, can_join_groups, can_read_all_group_messages, supports_inline_queries |
telegram_bot_send_message | Send a text message to a chat |
telegram_bot_send_photo | Send a photo (JPG/PNG, ≤5MB via URL) by HTTPS URL or by reusable file_id |
telegram_bot_send_document | Send a document (any type, ≤20MB via URL) by HTTPS URL or file_id |
telegram_bot_send_audio | Send an audio file (MP3, M4A, ≤20MB via URL) |
telegram_bot_send_voice | Send a voice note (OGG-Opus encoded) |
telegram_bot_send_video | Send a video (MP4, H |
telegram_bot_send_location | Send a location point |
telegram_bot_send_poll | Send a poll (regular or quiz) |
telegram_bot_edit_message_text | Edit the text of a previously-sent message (your bot's own messages only) |
telegram_bot_delete_message | Delete a message the bot sent (within ~48 hours for groups, anytime for own DMs) |
telegram_bot_get_chat | Fetch chat info: title, type (private/group/supergroup/channel), photo, description, invite_link, member_count, permissions |
telegram_bot_get_updates | Long-poll recent inbound messages (one-shot — pulls all updates since the last offset+1) |
FAQ
Unterstützen Gemini 1.5 Pro oder 2.x MCP? Ja — Gemini CLI ≥ 0.4 und die Vertex AI Tools API akzeptieren MCP httpUrl-Connectors mit Bearer-Header.
Nächste Schritte
War dieser Guide hilfreich?