scenario-testing vs Postman MCP Server
scenario-testing is a plugin bundle for AI coding tools published by 2389-research. 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-25. 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 |  scenario-testing |   Postman MCP Server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: dbb92f1 Forks (GitHub): 8 Stars (GitHub): 97 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 224 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 | scenario-testing | Postman MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 97 (worse) | 325 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 46 224 |
| Forks (GitHub) (differs) | 8 (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) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/2389-research/claude-plugins | github.com/postmanlabs/postman-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
scenario-testing
End-to-end testing with real dependencies - no mocks allowed; scenarios with real data are the only source of truth
Postman MCP Server
Give your AI agents trusted access to the full Postman platform.
How to run each
scenario-testing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install scenario-testing@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 scenario-testing publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of scenario-testing publish no settings it asks for, so we do not compare settings.
What it can do: scenario-testing · 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.