Ext Ops Panel
Open dashboard
Comparison

claude-telegram-voice-control vs BLEA

claude-telegram-voice-control is a plugin bundle for AI coding tools published by codefather-labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-telegram-voice-controlBLEA
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Downloads/month (PyPI): 423
Downloads/week (PyPI): 51
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

claude-telegram-voice-control vs BLEA
Factclaude-telegram-voice-controlBLEA
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)11 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (blea)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)32
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/codefather-labs/claude-telegram-voice-controlgithub.com/nitmi/blea
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-telegram-voice-control

In its own words, on Claude Code: claude-plugins-community:

Telegram channel with local voice transcription via whisper.cpp. Voice messages are automatically transcribed on-device using the Whisper medium model before being forwarded to Claude — no external APIs, no data leaves the machine. Cross-platform auto-install of whisper-cpp and ffmpeg. Gracefully degrades to standard behavior when dependencies are unavailable.

BLEA

In its own words, on Official MCP Registry:

Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.

How to run each

claude-telegram-voice-control As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-telegram-voice-control@claude-community

BLEA As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio blea -- uvx blea mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: claude-telegram-voice-control · What it can do: BLEA · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built