Ext Ops Panel
Open dashboard
Comparison

Postman MCP Server vs agent-device

Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). agent-device is an MCP server published by callstack. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplacePostman MCP Serveragent-device
Official MCP Registry Listed
Version: 2.13.0
Downloads/month (npm): 31 219
Downloads/week (npm): 4 519
Forks (GitHub): 87
Stars (GitHub): 319
Not marked · First seen
Listed
Version: 0.21.28
Downloads/month (npm): 979 627
Downloads/week (npm): 291 005
Forks (GitHub): 334
Stars (GitHub): 5 028
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:73f715030cbe
Forks (GitHub): 87
Pulls (Docker Hub): 45 254
Stars (Docker Hub): 6
Stars (GitHub): 319
Not marked · First seen
Not listed

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

Postman MCP Server vs agent-device
FactPostman MCP Serveragent-device
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)319 (worse)5 028 (better)
Pulls (Docker Hub) (differs)45 254No figure on Docker Hub
Forks (GitHub) (differs)87 (worse)334 (better)
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server or your machineOn your machine (agent-device)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)42Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/postmanlabs/postman-mcp-servergithub.com/callstack/agent-device
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Postman MCP Server

In its own words, on Official MCP Registry:

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

agent-device

In its own words, on Official MCP Registry:

MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps

How to run each

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

agent-device As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-device -- npx -y agent-device mcp

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

Tools each declares

The marketplaces of agent-device publish no list of tools, so we do not compare tools.

Settings each asks for

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

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

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