cctelegram

co8/cctelegram

3.2

If you are the rightful owner of cctelegram and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

CCTelegram is a comprehensive notification ecosystem designed to integrate Claude Code with Telegram using a Model Context Protocol (MCP) server and a high-performance bridge.

Tools
1
Resources
0
Prompts
0

CCTelegram GitHub Header

CCTelegram : Bridge + MCP Server

Bridge Version Claude Code

Rust TypeScript License Build Telegram

TL;DR

Complete Notification Ecosystem for Claude Code over Telegram

CCTelegram consists of two complementary components that work together seamlessly:

πŸ”Œ MCP Server (TypeScript) - Integrates directly with Claude Code via MCP protocol
πŸŒ‰ Bridge (Rust) - High-performance background service for Telegram communication

Get real-time notifications, interactive approvals, and comprehensive development workflow integration.
Built specifically for the Claude Code + developer mindset.

πŸ›‘οΈ Security Score: 8.5/10 (LOW RISK) | πŸ”’ OWASP Top 10 2021: 100% Compliant | βœ… Zero Critical Vulnerabilities

⚑ 30-Second Install

1. Get Telegram Ready

2. Install Complete System

# Download both MCP Server and built Bridge
git clone https://github.com/co8/cctelegram.git
cd cctelegram/mcp-server

# Install MCP Server + Slash Commands
./install.sh

# Configure your tokens (installer guides you)
export TELEGRAM_BOT_TOKEN="your_bot_token_here"
export TELEGRAM_ALLOWED_USERS="your_user_id_here"

# Bridge starts automatically in background

3. Test with Claude Code

# Restart Claude Code, then test with MCP tools:
@cctelegram send_telegram_message "πŸŽ‰ CCTelegram v1.9.0 Enterprise Testing Complete!"

πŸŽ‰ You should get a Telegram notification within seconds!

How it works: MCP Server processes the command in Claude Code β†’ Bridge detects the event file β†’ Sends to Telegram
Both components work together automatically - no manual management needed.

Architecture Diagram

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Claude Code   β”‚    β”‚   MCP Server    β”‚    β”‚   Bridge App    β”‚    β”‚  Telegram Bot   β”‚
β”‚                 β”‚    β”‚  (TypeScript)   β”‚    β”‚   (Rust Daemon) β”‚    β”‚                 β”‚
β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚    β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚    β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚    β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚
β”‚ β”‚MCP Tools    │◄┼────┼►│MCP Protocol │◄┼────┼►│File Watcher β”‚ β”‚    β”‚ β”‚Bot Client   β”‚ β”‚
β”‚ β”‚@cctelegram  β”‚ β”‚    β”‚ β”‚Handler      β”‚ β”‚    β”‚ β”‚             β”‚ β”‚    β”‚ β”‚             β”‚ β”‚
β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚ β””β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚ β””β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚ β””β”€β”€β”€β”€β”€β–²β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β”‚ β”Œβ”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β” β”‚    β”‚ β”Œβ”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β” β”‚    β””β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                       β”‚ β”‚Event File   β”‚ β”‚    β”‚ β”‚Event        β”‚ β”‚            β”‚
                       β”‚ β”‚Generator    β”‚ β”‚    β”‚ β”‚Processor    β”‚ β”‚    β”Œβ”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”
                       β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚ β””β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚  Telegram API β”‚
                       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β”‚ β”Œβ”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β” β”‚    β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜
                                              β”‚ β”‚Telegram Bot β”‚ β”‚            β”‚
           ~/.cc_telegram/                    β”‚ β”‚Client       β”‚ β”‚    β”Œβ”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”
      β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”                 β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚   User Device β”‚
      β”‚events/              │◄─────────────────                 β”‚    β”‚               β”‚
      β”‚β”œβ”€ task_123.json     β”‚                 β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚    β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚
      β”‚β”œβ”€ approval_456.json β”‚                 β”‚ β”‚Response     β”‚ β”‚    β”‚ β”‚Telegram   β”‚ β”‚
      │└─ progress_789.json β”‚                 β”‚ β”‚Handler      β”‚ β”‚    β”‚ β”‚App        β”‚ β”‚
      β”‚                     β”‚                 β”‚ β””β”€β”€β”€β”€β”€β–²β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚    β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
      β”‚responses/           │◄─────────────────       β”‚         β”‚    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
      β”‚β”œβ”€ approval_456.json β”‚                 β”‚       β”‚         β”‚
      │└─ command_890.json  β”‚                 β””β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
      β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜                         β”‚
                                               β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”
                                               β”‚  Response   β”‚
                                               β”‚   Files     β”‚
                                               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“± Live Notifications

Build SuccessSecurity AuditCode Review
Build SuccessSecurity AuditCode Review
βœ… Comprehensive build metricsπŸ›‘οΈ Zero-vulnerability reportsπŸ‘€ Detailed review summaries
Real-time CI/CD pipeline results with test coverage, bundle optimization, and deployment readinessOWASP-compliant security scans with vulnerability breakdown and compliance scoringPull request analysis with code quality metrics and approval workflows

πŸ” Interactive Approval Workflow

Initial Request and Response OptionsDetailed ReviewFinal Confirmation
Approval RequestRequest ApprovedApproved Response Confirmation
Denied Response Confirmation
πŸš€ Production DeploymentπŸ“‹ Comprehensive Detailsβœ… Confirmed Response
Critical changes with rating icons, pre-flight check status, and interactive approve/deny buttonsEnhanced authentication, performance improvements, security patches, and rollback planningReal-time confirmation with timestamp and deployment tracking

🎯 Key Features

  • πŸ›‘οΈ Zero Message Loss Architecture - NEW: Enterprise-grade reliability with comprehensive validation and deduplication
  • πŸ”” - Complete development lifecycle monitoring
  • πŸ”Œ MCP Server Integration - Zero-config Claude Code integration
  • πŸ“± Real-time Telegram Notifications - Instant alerts with rich formatting
  • βœ… Interactive Approvals - Approve deployments, code reviews via Telegram
  • ⚑ Performance Optimized - NEW: 86.3% payload reduction, microsecond serialization benchmarks
  • πŸ” Comprehensive Validation - NEW: 14 ValidationError types, field constraints, business logic validation
  • πŸ” Advanced Authentication - NEW: API keys, HMAC integrity, rate limiting
  • πŸ“Š Performance Monitoring - Built-in metrics, health checks, Prometheus integration
  • πŸ” Comprehensive Audit Logging - NEW: Secure event tracking, data sanitization

β†’ - Complete feature reference


πŸ›‘οΈ Enterprise Reliability

Zero Message Loss Achievement - Comprehensive reliability improvements targeting 100% message delivery:

🎯 Validation & Integrity System

  • 14 ValidationError Types with user-friendly messages and severity classification
  • Field Constraint Validation - Title (1-200 chars), description (1-2000 chars), UUID/timestamp validation
  • Business Logic Validation - Event type-specific rules and required field checking
  • Data Consistency Validation - Cross-field validation and logical consistency verification

πŸ”„ Advanced Deduplication

  • Primary Deduplication - Exact event_id matching for duplicate prevention
  • Secondary Deduplication - Content-based matching within configurable time windows (5 seconds default)
  • Intelligent Detection - Hash-based content comparison for efficient duplicate identification

⚑ Performance Optimization

  • 86.3% Payload Reduction - Intelligent null field omission and optimized JSON structure
  • Serialization Benchmarks - Average 72.82ΞΌs serialization, 60.549ΞΌs deserialization
  • Forward Compatibility - Custom deserializers with Unknown variant fallbacks
  • Snake_case Consistency - Standardized JSON field naming across all structures

πŸ“Š Comprehensive Test Suite

  • 154 Tests (152% increase) with comprehensive validation and reliability testing
  • 100% Test Success Rate - All core functionality verified and working
  • Cross-Platform E2E Testing - Chrome, Firefox, Safari compatibility verified
  • Performance Benchmarks - Serialization/deserialization timing integrated into test suite
  • API Validation - Health endpoints, metrics, and error handling tested
  • Visual Regression Testing - UI components and mobile responsiveness verified

πŸ§ͺ Quality Assurance & Testing

βœ… Complete Test Coverage (154 Tests Passing)

Rust Library Tests: 122/122 βœ…

  • Core integrity validation and cryptographic functions
  • Event processing and queue management systems
  • Compression and deduplication algorithms
  • Security authentication and authorization
  • Performance monitoring and metrics collection

End-to-End Tests: 32/32 βœ…

  • Bridge health API endpoints validation
  • Dashboard UI responsiveness (mobile/desktop)
  • Cross-browser compatibility (Chrome/Firefox/Safari)
  • Network failure recovery scenarios
  • Visual regression testing with screenshot comparison
  • Performance benchmarking under various conditions

Test Categories:

πŸ¦€ Rust Unit Tests        122 βœ…  # Core business logic
🌐 E2E Integration Tests   32 βœ…  # Full system workflows
πŸ“± Cross-Platform Tests    15 βœ…  # Multi-browser support
πŸ”„ Performance Tests        8 βœ…  # Load & stress testing
🎨 Visual Regression        6 βœ…  # UI consistency checks
⚑ API Validation Tests     5 βœ…  # Endpoint functionality

Quality Gates:

  • 100% Core Test Success - All critical path functionality verified
  • Performance Standards - Load times <3s, API responses <200ms
  • Error Handling - Graceful degradation and recovery verified

πŸ“ Project Structure

cctelegram/
β”œβ”€β”€ docs/                      # πŸ“š Unified Documentation Hub
β”‚   β”œβ”€β”€ API_REFERENCE.md       # πŸ”Œ Tools & Events Reference
β”‚   β”œβ”€β”€ INSTALLATION.md        # ⚑ Setup Guide
β”‚   β”œβ”€β”€ TROUBLESHOOTING.md     # πŸ”§ Problem Solving
β”‚   β”œβ”€β”€ SECURITY.md            # πŸ›‘οΈ Security & Compliance
β”‚   β”œβ”€β”€ CONTRIBUTING.md        # 🀝 Developer Guide
β”‚   β”œβ”€β”€ assets/                # πŸ“Έ Screenshots & Images
β”‚   β”œβ”€β”€ components/            # 🧩 Component Documentation
β”‚   β”‚   β”œβ”€β”€ mcp-server.md      # MCP Server Guide
β”‚   β”‚   β”œβ”€β”€ benchmarking.md    # Performance Testing
β”‚   β”‚   └── observability.md   # Monitoring & Metrics
β”‚   β”œβ”€β”€ testing/               # πŸ§ͺ Testing Documentation
β”‚   β”‚   β”œβ”€β”€ emulation.md       # Bot API Emulation
β”‚   β”‚   β”œβ”€β”€ playwright.md      # E2E Testing
β”‚   β”‚   β”œβ”€β”€ chaos-engineering.md # Chaos Testing
β”‚   β”‚   └── contract-testing.md  # Contract Testing
β”‚   └── mcp-server/            # πŸ“– MCP Server Technical Docs
β”‚       β”œβ”€β”€ api/               # API Documentation
β”‚       β”œβ”€β”€ deployment/        # Deployment Guides
β”‚       β”œβ”€β”€ guide/             # User Guides
β”‚       └── examples/          # Code Examples
β”œβ”€β”€ src/                       # πŸ¦€ Rust Bridge Source
β”‚   β”œβ”€β”€ config/                # βš™οΈ Configuration Management
β”‚   β”œβ”€β”€ events/                # πŸ“‘ Event Processing & Queuing
β”‚   β”œβ”€β”€ storage/               # πŸ’Ύ Persistence & Compression
β”‚   β”œβ”€β”€ telegram/              # πŸ“± Telegram Bot Integration
β”‚   β”œβ”€β”€ mcp/                   # πŸ”Œ MCP Protocol Support
β”‚   β”œβ”€β”€ tier_orchestrator/     # πŸŽ›οΈ Advanced Orchestration
β”‚   └── utils/                 # πŸ› οΈ Utilities & Health Checks
β”œβ”€β”€ mcp-server/                # πŸ”Œ MCP Server (TypeScript)
β”‚   β”œβ”€β”€ src/                   # πŸ’Ό Server Implementation
β”‚   β”œβ”€β”€ scripts/               # πŸš€ Build & Deploy Tools
β”‚   └── install.sh             # ⚑ One-click installer
β”œβ”€β”€ tests/                     # 🎭 Unified Testing Hub
β”‚   β”œβ”€β”€ mcp-server/            # MCP Server Test Suite
β”‚   β”‚   β”œβ”€β”€ unit/              # Unit Tests
β”‚   β”‚   β”œβ”€β”€ integration/       # Integration Tests
β”‚   β”‚   β”œβ”€β”€ e2e/               # End-to-End Tests
β”‚   β”‚   β”œβ”€β”€ performance/       # Performance Tests
β”‚   β”‚   β”œβ”€β”€ chaos/             # Chaos Engineering
β”‚   β”‚   └── contract/          # Contract Testing
β”‚   β”œβ”€β”€ playwright/            # 🎯 E2E Browser Tests
β”‚   β”œβ”€β”€ emulation/             # πŸ“‘ Bot API Emulation
β”‚   β”œβ”€β”€ *.rs                   # Rust Integration Tests
β”‚   └── *.sh                   # Test Scripts
β”œβ”€β”€ examples/                  # πŸ’‘ Usage Examples & Demos
β”œβ”€β”€ scripts/                   # βš™οΈ Automation Scripts
β”œβ”€β”€ monitoring/                # πŸ“Š Prometheus & Grafana
β”œβ”€β”€ target/                    # πŸ—οΈ Rust Build Artifacts
└── .taskmaster/               # πŸ“‹ Task Master Integration

πŸ“š Documentation

Complete documentation in 7 focused files:

Get StartedPower UsersContributors & Operators

Project overview & quick start

All 20+ tools & 44+ events

Developer guide & workflows

Complete setup in <10 minutes

Problem-solving & diagnostics

Technical design & system overview

Security policy & compliance

Total documentation: 2,400+ lines across 7 core files plus comprehensive component & testing docs (streamlined from 10,000+ lines across 97+ files)

🎨 Visual System Overview

graph LR
    A[πŸ‘©β€πŸ’» Claude Code] -->|MCP Protocol| B[πŸ”Œ MCP Server v1.9.0]
    B -->|Event Files| C[πŸŒ‰ Bridge v0.9.0]
    C -->|Bot API| D[πŸ“± Telegram]

    style A fill:#FF8C42,color:#fff
    style B fill:#2da199,color:#fff
    style C fill:#FF6B6B,color:#fff
    style D fill:#26A5E4,color:#fff

🎯 Streamlined Documentation Experience:

  • - Gateway with performance stats and user routing
  • - Complete setup guide with 95% success rate
  • - Comprehensive tool and event catalog
  • - Practical problem-solving guide
  • - Complete developer lifecycle guide
  • - Production security and compliance

πŸ’‘ Quick Example

Task Completion Notification:

# Your build system creates this file when a task completes:
echo '{
  "type": "task_completion",
  "source": "ci_system",
  "title": "βœ… Deploy Complete",
  "description": "Production deployment v2.1.0 successful"
}' > ~/.cc_telegram/events/deploy-complete.json

# CCTelegram instantly sends: "βœ… Deploy Complete ⏰ 14:30 UTC
# Production deployment v2.1.0 successful"

Performance Alert:

# Monitoring system triggers alert:
echo '{
  "type": "performance_alert",
  "title": "⚠️ Memory High",
  "description": "Server memory usage: 85% (threshold: 80%)"
}' > ~/.cc_telegram/events/memory-alert.json

# Get instant notification with threshold details

βš™οΈ Alternative Installation

Manual Bridge Setup (Advanced Users):

# Download and extract latest release
# Get the latest release URL automatically
LATEST_URL=$(curl -s https://api.github.com/repos/co8/cctelegram/releases/latest | grep "tarball_url" | cut -d '"' -f 4)
curl -L "$LATEST_URL" -o cctelegram-latest.tar.gz
tar -xzf cctelegram-latest.tar.gz
cd co8-cctelegram-*
cargo build --release

# Configure and run
export TELEGRAM_BOT_TOKEN="your_bot_token_here"
export TELEGRAM_ALLOWED_USERS="your_user_id_here"
./target/release/cctelegram-bridge

# Test with file creation
mkdir -p ~/.cc_telegram/events
echo '{"type": "task_completion", "title": "Bridge Test", "description": "Manual setup working"}' > ~/.cc_telegram/events/test.json

Build from Source:

git clone https://github.com/co8/cctelegram.git
cd cctelegram
cargo build --release
./target/release/cctelegram-bridge

Built with ❀️ in Rust | πŸ”’ Enterprise Security | βœ… OWASP Compliant | πŸ›‘οΈ Zero Critical Vulnerabilities