Deployment · Personal Account Proxy

Let AI securely operate
your Telegram

Deploy a dedicated Telegram personal account proxy with one click. After QR code authorization, use standard MCP or REST to read chats, search history, and handle messages; each tenant has an independent container, credentials, and persistent volume.

Deploy NowView Integration Documentation
14REST operations
MCPstandard protocol
1:1tenant isolation
QRQR code authorization

Real personal account capabilities, powered by your AI

Not a Bot API bot, but a personal account proxy authorized by you via QR code. Ideal for personal information assistants, message search, customer communication, and workflow automation.

01

Read, search, and organize messages

List recent chats and unread messages, read history, search individual or all chats by keyword, and retrieve contact information.

02

Operate as yourself

After explicit authorization, send, reply to, edit, and delete messages, add emoji reactions, and mark chats as read.

03

Both MCP and REST endpoints

Claude Code, IDE Agents, and other MCP clients can connect directly; standard applications can also call equivalent REST APIs.

04

QR code and two-factor authentication

After deployment, scan the QR code directly with the Telegram client. If 2FA is enabled, complete verification on the same page; passwords are not written to platform configuration.

05

Persistent login session storage

Sessions are stored in a tenant-dedicated persistent volume, so there is no need to scan again after Pod restarts or version upgrades; they are deleted when the instance is destroyed.

06

Unauthorized access denied by default

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

Get connected in three steps

No need to generate a Session locally or paste a complete login session into the platform.

Create a dedicated instance

Create an application in the console and activate a subscription, then click Deploy to create a dedicated instance.

Authorize your account via QR code

Open Telegram “Settings → Devices → Link Desktop Device” and scan the console QR code.

Connect your AI

Copy the MCP address and Bearer token to let your Agent call Telegram tools.

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

Capabilities

The same capabilities are shared by MCP tools and the REST API, avoiding behavior drift between two implementations.

CategoryActionsTypical Uses
AccountQR code login, status, 2FA, logout, whoamiLifecycle and identity verification
ConversationsList conversations, unread filtering, contactsInbox overview and task routing
ReadRead history, conversation search, global searchSummaries, knowledge retrieval, follow-up reminders
WriteSend, reply, edit, delete, react, mark as readConfirmed messaging collaboration and automation

Security and Usage Boundaries

Tenant-Level Isolation

Each Application has its own Helm Release, PVC, Ingress, and access token, with no shared Telegram login session.

Credentials Are Not Stored in Page Configuration

QR code tokens, 2FA passwords, and MTProto sessions are not written to Application configuration or frontend local storage.

Responsible Use

Only connect accounts that you own and are authorized to use. Do not use for spam, unsolicited bulk direct messages, or bypassing Telegram restrictions.

Frequently Asked Questions

How is it different from a Telegram Bot?

The Bot API represents a bot account; this service uses your QR code authorization for a personal account, so it can access personal conversations and contacts.

Do I need to scan the QR code again after restarting?

Normally, no. The session is stored in a dedicated persistent volume; reauthorization is only required after you actively log out or the session expires.

Will AI automatically send messages to anyone?

The agent provides sending capabilities, but the Agent should obtain explicit confirmation before sending to third parties. The platform does not initiate messages on its own.

How do I revoke access?

You can log out in the console or destroy the instance, or terminate the session in Telegram under “Settings → Devices”.

Connect Telegram to Your Agent

Deploy a dedicated agent in minutes. After scanning the QR code, securely use personal account capabilities through MCP or REST.

Create a Telegram Agent