Ext Ops Panel
Open dashboard
Comparison

tg-agent vs Postman MCP Server

tg-agent is a plugin bundle for AI coding tools published by axisrow. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-17. 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
Marketplacetg-agentPostman MCP Server
Community marketplace axisrow/tg_content_factory Listed
Version: 0.2.4.1
Forks (GitHub): 7
Stars (GitHub): 33
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.14.0
Downloads/month (npm): 31 219
Downloads/week (npm): 4 519
Forks (GitHub): 87
Stars (GitHub): 321
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:73f715030cbe
Forks (GitHub): 87
Pulls (Docker Hub): 45 316
Stars (Docker Hub): 6
Stars (GitHub): 321
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

tg-agent vs Postman MCP Server
Facttg-agentPostman MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)33 (worse)321 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub45 316
Forks (GitHub) (differs)7 (worse)87 (better)
Last release (differs)2026-10-15 (worse)2026-10-16 (better)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published42
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/axisrow/tg_content_factorygithub.com/postmanlabs/postman-mcp-server
Changes in the last 7 days (differs)31
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 h 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

tg-agent

In its own words, on Community GitHub marketplaces:

Full-spectrum Telegram access for coding agents through the tg-agent CLI: channels, chats, messages, media, admin, content pipelines, analytics.

Postman MCP Server

In its own words, on Official MCP Registry:

Give your AI agents trusted access to the full Postman platform.

How to run each

tg-agent As a Claude Code plugin

Claude Code
/plugin marketplace add axisrow/tg_content_factory
/plugin install tg-agent@tg-agent-marketplace

Postman MCP Server As a remote MCP server

Claude Code
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 tg-agent publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of tg-agent publish no settings it asks for, so we do not compare settings.

What it can do: tg-agent · What it can do: Postman MCP Server · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built