telegram-per-project
trezero v1.1.0
Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach Terminal 1 and messages t...
From the developer
License
MIT
Declared components
Mcp servers · Channels
Works with
Claude Code
Description
From the marketplace listing
Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach Terminal 1 and messages to @beta_bot reach Terminal 2, with no cross-talk. Key features: - Per-project bot tokens via TELEGRAM_PROJECT_ID environment variable - Independent access policies per project, bootstrapped from global config - Response timeout — notifies senders when the assistant isn't responding (configurable, default 45s) - Full access control: DM pairing, allowlists, group mention detection - Reply, react, and edit_message tools for the assistant - Photo support with inline preview - Fully backward compatible — works as a single global bot if no project ID is set
What changed
No changes recorded yet. Follow this plugin to keep track of future changes.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Let multiple Claude Code sessions talk to each other across projects. Each session gets a name, sends messages, checks its inbox, and see...
Shared terms: gets, inbox, message, project
-
Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.
Shared terms: channel, policy, telegram, code
-
Rust-based Telegram channel for Claude Code. Drop-in replacement for the official Bun-based Telegram plugin — same features, 20x lighter....
Shared terms: channel, telegram, code, message
-
Feishu (Lark) channel for Claude Code — messaging bridge that connects a Feishu bot to Claude Code via MCP server. Receives messages thro...
Shared terms: bot, channel, message, code
-
MQTT channel plugin for Claude Code. Bridges MQTT messages into Claude Code sessions via the MCP channel protocol, enabling cross-session...
Shared terms: channel, cross, message, code
Keywords
Files & skills
telegram-per-project · catalog manifest
Saved declaration
{}
telegram-per-project · catalog manifest
Saved declaration
{
"name": "telegram-per-project",
"source": {
"sha": "c2c2d391f342f932809292b29a82df7bc8fa68d5",
"url": "https://github.com/trezero/telegram-per-project.git",
"source": "url"
},
"homepage": "https://github.com/trezero/telegram-per-project#readme",
"description": "Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach Terminal 1 and messages to @beta_bot reach Terminal 2, with no cross-talk. \n\nKey features: \n - Per-project bot tokens via TELEGRAM_PROJECT_ID environment variable\n - Independent access policies per project, bootstrapped from global config\n - Response timeout — notifies senders when the assistant isn't responding (configurable, default 45s)\n - Full access control: DM pairing, allowlists, group mention detection \n - Reply, react, and edit_message tools for the assistant \n - Photo support with inline preview \n - Fully backward compatible — works as a single global bot if no project ID is set"
}
telegram-per-project · catalog manifest
Mcp servers
{
"telegram": {
"cwd": "${CLAUDE_PLUGIN_ROOT}",
"env": {
"NODE_PATH": "${CLAUDE_PLUGIN_DATA}/node_modules"
},
"args": [
"server.ts"
],
"command": "bun"
}
}Channels
[
{
"server": "telegram",
"userConfig": {
"bot_token": {
"sensitive": true,
"description": "Telegram bot token from @BotFather (e.g. 123456789:AAH...)"
}
}
}
]
Saved declaration
{
"name": "telegram-per-project",
"author": {
"name": "trezero"
},
"license": "MIT",
"version": "1.1.0",
"channels": [
{
"server": "telegram",
"userConfig": {
"bot_token": {
"sensitive": true,
"description": "Telegram bot token from @BotFather (e.g. 123456789:AAH...)"
}
}
}
],
"keywords": [
"telegram",
"messaging",
"channel",
"mcp",
"per-project",
"multi-bot"
],
"mcpServers": {
"telegram": {
"cwd": "${CLAUDE_PLUGIN_ROOT}",
"env": {
"NODE_PATH": "${CLAUDE_PLUGIN_DATA}/node_modules"
},
"args": [
"server.ts"
],
"command": "bun"
}
},
"repository": "https://github.com/trezero/telegram-per-project",
"description": "Telegram channel for Claude Code with per-project bot isolation — each project gets its own bot, access policy, and message inbox."
}
plugin.json observed Nov 6, 2026 · 10:49 UTC. Manifest source ↗
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
Installation instructions
Community
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram-per-project@claude-community
Technical details
- Sources
- Community
- First seen
- Oct 3, 2026 · 22:13 UTC
- Last seen
- Nov 7, 2026 · 06:00 UTC
- Latest observed change
- Oct 3, 2026 · 22:13 UTC
- Collection status
- Listed
- Reported installs
- Not provided
Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.
Download plugin data (JSON)Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.