Telegram Native MCP Documentation
The Telegram AI mcp for channel broadcasting, conversation routing, audience pulse tracking, and mcp analytics.
Overview
Telegram Native MCP is the SSNATW AI mcp for Telegram. It gives the platform a dedicated runtime for conversation intelligence and routing, so the experience feels native, fast, and fully integrated with the rest of the product.
The mcp follows the same marketplace installation and agent attachment model used across SSNATW. After activation, it can run under standard permissions or under ranks that include root access, which can manage the full mcp lifecycle, credentials, recovery actions, and advanced controls.
This guide documents the mcp as a live product capability. It covers what the mcp does, what users can expect to see, which service endpoints support it, and how the core runtime objects are structured.
What this mcp delivers
- AI-assisted broadcast handling for channels and groups.
- More consistent routing for chat-heavy Telegram workflows.
- Better audience pulse tracking inside the dashboard.
User-facing signals
- Broadcast reach
- Chat activity
- Audience return behavior
Capabilities
Telegram Native MCP is designed as a first-class AI mcp. The workflow below describes how the runtime, user experience, and management layer fit together in production.
- Install the mcp and bind it to the Telegram-facing agent.
- Set AI policy for channels, groups, broadcasts, and response behavior.
- Read Telegram insight signals for broadcast reach, activity, and return behavior.
API Surface
The mcp surface is split into marketplace APIs for discovery and installation, runtime APIs for AI execution and analytics, and management APIs for configuration and advanced control.
| Surface | Method | Path | Purpose |
|---|---|---|---|
| marketplace | GET | /api/marketplace/mcp | List mcp offers available in the marketplace catalog. |
| marketplace | GET | /api/marketplace/mcp/:id | Read the marketplace record for Telegram Native MCP. |
| marketplace | POST | /api/marketplace/mcp/install | Install the mcp to a private agent or shared agent. |
| management | GET | /api/agents/:agent_id/mcp | List mcp attachments on a private agent. |
| management | GET | /api/shared-agents/:agent_id/mcp | List mcp attachments on a shared agent. |
| runtime | POST | /api/mcp/native-telegram/runtime/execute | Execute an AI action such as publish, reply, score, route, or monetize depending on the mcp family. |
| runtime | GET | /api/mcp/native-telegram/runtime/insights | Read insight data used by analytics cards, trends, and detail views. |
| management | GET | /api/mcp/native-telegram/management/config | Read active runtime policy, access tier, and mcp configuration. |
| management | PUT | /api/mcp/native-telegram/management/config | Update runtime policy, AI behavior rules, and mcp settings. |
Function Calls and Integration Examples
The following snippets show the mcp from a real integration perspective: install it, read its attached state, then drive runtime behavior and analytics through explicit service calls.
Install through the marketplace API
import { installMarketplaceMcp } from '../api/marketplace';
await installMarketplaceMcp({
offerId: <mcp-id>,
agentUuid: '<agent-uuid>',
installMode: 'purchase',
notes: 'Enable Telegram Native MCP on the primary Telegram agent.'
});Read installed attachment state
import { listAgentMcps } from '../api/agents';
const attachments = await listAgentMcps(<agent-id>);
const installed = attachments.find((item) => item.offer_slug === 'native-telegram');
if (installed?.status === 'active') {
console.log('Telegram Native MCP is live on this agent');
}Execute the AI runtime and read insights
import { apiFetch } from '../api/client';
await apiFetch('/api/mcp/native-telegram/runtime/execute', {
method: 'POST',
body: JSON.stringify({
agent_uuid: '<agent-uuid>',
intent: 'route_conversation',
context: {
platform: 'telegram',
priority: 'high',
resource: 'conversation-snapshot',
conversation_id: '<conversation-id>'
}
})
});
const insights = await apiFetch('/api/mcp/native-telegram/runtime/insights');
console.log(insights.summary);MCP Data Structures
These structures define the core mcp object, the installed attachment record, and the runtime data shape used by the AI orchestration and analytics layers.
Marketplace mcp record
The catalog object returned by the marketplace mcp APIs.
export interface MarketplaceMcpRecord {
id: number;
slug: 'native-telegram';
name: 'Telegram Native MCP';
version: string;
status: 'active' | 'published' | 'beta' | 'deprecated';
description: string;
author?: string | null;
mcp_type: 'social';
platform: 'telegram';
capabilities: string[];
required_permissions: string[];
documentation_url?: string | null;
pricing_model?: 'free' | 'one_time' | 'subscription' | 'revenue_share';
price?: number | null;
revenue_share_percent?: number | null;
is_official?: boolean;
install_count?: number;
rating?: number;
review_count?: number;
created_at?: string;
updated_at?: string;
}Agent mcp attachment
The normalized attachment object created after installation.
export interface AgentMcpAttachment {
id: number;
agent_id: number;
offer_id: number;
offer_name: string;
offer_slug: string;
status: string;
install_mode: 'trial' | 'purchase' | 'queued';
billing_model: string;
revenue_share_percent?: number | null;
upfront_price?: number | null;
notes?: string | null;
created_at: string;
activated_at?: string | null;
}MCP runtime insight payload
The runtime object used by the AI execution and analytics layers.
export interface McpRuntimeInsight {
mcp_slug: 'native-telegram';
platform: 'telegram';
agent_uuid: string;
status: 'active' | 'degraded' | 'paused';
summary: string;
metrics: {
reply_rate: 0.81,
queue_pressure: 22,
conversations_active: 184
};
controls: {
automation_mode: 'assisted' | 'autonomous' | 'priority';
access_tier: 'standard' | 'root';
};
updated_at: string;
}MessagingSnapshot
A conversation-level payload for message queue state, routing outcome, and reply performance.
export interface MessagingSnapshot {
mcp_slug: 'native-telegram';
platform: 'telegram';
conversation_id: string;
queue_state: 'open' | 'pending' | 'escalated' | 'closed';
assigned_route: 'ai' | 'hybrid' | 'human';
reply_rate: number;
queue_pressure: number;
last_message_at: string;
updated_at: string;
}MCP Lifecycle
- Discover the mcp in the marketplace and open its detail page.
- Install it to the target private agent or shared agent through the marketplace installation flow.
- Activate the runtime profile, channel policy, and AI behavior rules that define how the mcp should operate.
- Allow the mcp to execute publishing, messaging, visibility, or monetization tasks through the AI runtime layer.
- Review health, insights, and control status through the mcp management surface.
- Scale, refine, or override behavior as needed through standard controls or rank-based root access.
Platform Notes
- Telegram should remain the canonical platform identifier across routing, analytics, caching, and UI state.
- The user-facing dashboard should stay focused on clear outcomes and not drown the account in low-level noise.
- Configuration, credentials, and advanced controls should stay consistent across marketplace, runtime, and management surfaces.
- Ranks that include root access are allowed to manage installation, runtime policy, credentials, execution controls, analytics settings, and recovery actions across the full mcp surface.
- MCP schemas should stay additive and versionable so the runtime can evolve without breaking existing agents or dashboards.
