telegram-per-project vs Postman MCP Server
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). Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-26. 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 |   Postman MCP Server |
|---|---|---|
| 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: 2.14.0 Downloads/month (npm): 31 313 Downloads/week (npm): 4 401 Forks (GitHub): 88 Stars (GitHub): 325 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:73f715030cbe Forks (GitHub): 88 Pulls (Docker Hub): 46 345 Stars (Docker Hub): 6 Stars (GitHub): 325 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 | Postman MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 325 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 46 345 |
| Forks (GitHub) (differs) | 0 (worse) | 88 (better) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 42 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/trezero/telegram-per-project | github.com/postmanlabs/postman-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
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
Postman MCP Server
Give your AI agents trusted access to the full Postman platform.
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-communityPostman MCP Server As a remote MCP server
claude mcp add --transport http postman-mcp-server https://mcp.postman.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: POSTMAN_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Postman MCP Server has a remote endpoint we check. How we check endpoints
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 Postman MCP Server asks for
POSTMAN_API_KEY (secret)
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: Postman MCP Server · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.