telegram-per-project vs Perplexity API Platform
telegram-per-project is a plugin bundle for AI coding tools published by trezero. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Perplexity API Platform is an MCP server published by perplexity.ai. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. 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
| Marketplace |  telegram-per-project |   Perplexity API Platform |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.1 Downloads/month (npm): 102 467 Downloads/week (npm): 16 084 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:7816f45a6f26 Forks (GitHub): 387 Pulls (Docker Hub): 80 959 Stars (Docker Hub): 17 Stars (GitHub): 2 589 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
| Fact | telegram-per-project | Perplexity API Platform |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 2 589 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 80 959 |
| Forks (GitHub) (differs) | 0 (worse) | 387 (better) |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@perplexity-ai/mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 3 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Hooks it runs | 1 | 1 |
| Parts of the bundle (differs) | 4 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/trezero/telegram-per-project | github.com/ppl-ai/modelcontextprotocol |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-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
telegram-per-project
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
Perplexity API Platform
Real-time web search, reasoning, and research through Perplexity's API
How to run each
telegram-per-project As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram-per-project@claude-communityPerplexity API Platform As a local MCP server: npm package
claude mcp add --transport stdio perplexity-api-platform -- npx -y @perplexity-ai/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of telegram-per-project publish no list of tools, so we do not compare tools.
Settings each asks for
Only telegram-per-project asks for
NODE_PATH
Only Perplexity API Platform asks for
PERPLEXITY_API_KEY (secret)PERPLEXITY_TIMEOUT_MS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: telegram-per-project · What it can do: Perplexity API Platform · 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 Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.