Deployment · Personal Account Proxy

Let AI Operate Safely
Your Telegram

One-click deployment of a dedicated Telegram personal account proxy. After scanning the code for authorization, read sessions, retrieve history, and process messages through standard MCP or REST; each tenant has an independent container, independent credentials, and independent persistent volume.

Deploy Now View Integration Documentation

14REST Operations

MCPStandard Protocol

1:1Tenant Isolation

QRScan Authorization

Real Personal Account Capabilities, Handed to Your AI

Not a Bot API robot, but a personal account proxy authorized by you through scanning. Suitable for personal information assistants, message retrieval, customer communication, and workflow automation.

Read, Search, Organize Messages

List recent conversations and unread messages, read history, search individual or all conversations by keywords, and obtain contact information.

Operate as Yourself

Send, reply, edit, and delete messages after clear authorization, add emoji responses, and mark conversations as read.

MCP and REST Dual Exit

Claude Code, IDE Agent, and other MCP clients can connect directly; regular applications can also call equivalent REST interfaces.

Scan and Two-Step Verification

After deployment, scan the code directly with the Telegram client. If 2FA is enabled, complete verification on the same page, and the password is not written into the platform configuration.

Persistent Login State

Sessions are stored in tenant-specific persistent volumes, and no need to rescan after Pod restarts and version upgrades; deleted when instances are destroyed.

Default Denial of Unauthorized Access

Except for health checks, MCP, REST, and login interfaces require independent Bearer tokens; anonymous requests fail by default.

Complete Integration in Three Steps

No need to generate a Session locally, nor to paste the complete login state into the platform.

Create a Dedicated Instance

Select specifications in the console, and the platform will automatically create containers, Ingress, and persistent volumes.

Scan to Authorize Account

Open Telegram "Settings → Devices → Link Desktop Devices", and scan the console QR code.

Connect Your AI

Copy the MCP address and Bearer token to allow the Agent to call the Telegram tool.

{
  "mcpServers": {
    "telegram": {
      "url": "https://telegram-bot-<your-id>.app.acedata.cloud/mcp",
      "headers": { "Authorization": "Bearer <YOUR_PROXY_TOKEN>" }
    }
  }
}

Capability List

The same capabilities are shared by the MCP tool and REST API to avoid behavioral drift between two sets.

Category	Operation	Typical Use
Account	Scan login, status, 2FA, logout, whoami	Lifecycle and identity confirmation
Session	List sessions, unread filter, contacts	Inbox overview and task distribution
Read	Read history, session search, global search	Summarization, knowledge retrieval, follow-up reminders
Write	Send, reply, edit, delete, respond, read	Confirmed message collaboration and automation

Security and Usage Boundaries

Tenant-Level Isolation

Each Application corresponds to an independent Helm Release, PVC, Ingress, and access token, without sharing Telegram login states.

Credentials Do Not Enter Page Configuration

QR code token, 2FA password, and MTProto session will not be written into Application configuration or front-end local storage.

Responsible Use

Only connect accounts that you own and have authorized. Must not be used for spam messages, unsolicited bulk messaging, or circumventing Telegram restrictions.

Frequently Asked Questions

What is the difference between this and a Telegram Bot?

The Bot API represents bot accounts; this service is authorized by scanning your personal account, thus allowing access to personal sessions and contacts.

Do I need to scan again after a restart?

Normally, no. Sessions are stored in independent persistent volumes; re-authorization is only required when actively logging out or when the session expires.

Will the AI automatically send messages to anyone?

The proxy provides sending capabilities, but the Agent should perform explicit confirmation before sending to third parties. The platform will not initiate messages on its own.

How to revoke access?

You can log out in the console or destroy the instance, or you can go offline in the session under Telegram "Settings → Devices".

Integrate Telegram with Your Agent

Deploy a dedicated proxy in minutes, and after scanning, you can securely use personal account capabilities through MCP or REST.

Create Telegram Proxy

Let AI Operate SafelyYour Telegram

telegram-bot

Playground

Input

Result

API

Pricing

Packages

Route pricing

Request calculator

Overview

telegram-bot

Model facts