| name | telegram-mcp-connector |
| description | MCP connector for Telegram Bot API – enables AI-powered bot management, message handling, and group administration through Claude |
| license | GPL/API |
| tags | ["dev","communication","mcp","telegram","bot"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Telegram MCP Connector
Overview
This skill enables Claude to interact with Telegram through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Telegram's Bot API, allowing natural language control of Telegram operations, intelligent automation, and AI-powered assistance for Telegram workflows.
When to Use This Skill
- Bot creation and command configuration
- Group and channel management
- Inline query handling and response generation
- Media processing and file management
- Webhook and polling configuration
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Telegram │
│ (Client) │◀────│ (TypeScript) │◀────│ (Bot API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Telegram operations as tools Claude can invoke. The server translates natural language intentions into Bot API calls.
Key Endpoints/Interfaces
sendMessage, getUpdates, setWebhook, getChatMember, sendDocument
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "telegram-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Telegram resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}sendMessage`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"telegram-mcp-connector": {
"command": "node",
"args": ["path/to/telegram-mcp-connector/index.js"],
"env": {
"TELEGRAM_API_KEY": "your-api-key",
"TELEGRAM_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Telegram API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Telegram API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a Telegram bot that responds to /summary command with a digest of recent channel messages"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
