Postman MCP Server vs Apify
Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, npm registry (MCP servers)). Apify is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |   Postman MCP Server |  Apify |
|---|---|---|
| Official MCP Registry | Listed Version: 2.15.0 Downloads/month (npm): 33 131 Downloads/week (npm): 7 080 Forks (GitHub): 87 Stars (GitHub): 326 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:73f715030cbe Forks (GitHub): 87 Pulls (Docker Hub): 47 399 Stars (Docker Hub): 6 Stars (GitHub): 326 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 2.15.0 Downloads/month (npm): 33 131 Downloads/week (npm): 7 080 Forks (GitHub): 87 Stars (GitHub): 326 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
| Fact | Postman MCP Server | Apify |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 326 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 47 399 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 87 (better) | 0 (worse) |
| Last release (differs) | 2026-10-30 (worse) | 2026-10-30 (better) |
| Where it runs (differs) | Remote server or your machine | Remote server (gateway.pipeworx.io/apify/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/postmanlabs/postman-mcp-server | github.com/pipeworx-io/mcp-apify |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 40 h ago returned HTTP 401 | Status out of date: last check 33 h ago returned HTTP 200 |
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
Give your AI agents trusted access to the full Postman platform.
Apify
Apify MCP — run web-scraping Actors and fetch their dataset results.
How to run each
Postman 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
Apify As a remote MCP server
claude mcp add --transport http apify https://gateway.pipeworx.io/apify/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only Postman MCP Server has
createCollectioncreateCollectionRequestcreateCollectionResponsecreateEnvironmentcreateMockcreateSpeccreateSpecFilecreateWorkspaceduplicateCollectiongenerateCollectiongenerateSpecFromCollectiongetAllSpecs
Show the remaining 30
getAuthenticatedUsergetCollectiongetCollectionsgetDuplicateCollectionTaskStatusgetEnabledToolsgetEnvironmentgetEnvironmentsgetGeneratedCollectionSpecsgetMockgetMocksgetSpecgetSpecCollectionsgetSpecDefinitiongetSpecFilegetSpecFilesgetTaggedEntitiesgetWorkspacegetWorkspacespublishMockputCollectionputEnvironmentrunCollectionsearchPostmanElementssyncCollectionWithSpecsyncSpecWithCollectionupdateCollectionRequestupdateMockupdateSpecFileupdateSpecPropertiesupdateWorkspace
Only Apify has
ai_visibility_checkapify_dataset_itemsapify_run_actorapify_scrape_urlarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_facts
Show the remaining 33
company_register_searchcompare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Apify as of 2026-10-24). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only Postman MCP Server asks for
POSTMAN_API_KEY (secret)
Only Apify asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Postman MCP Server · What it can do: Apify · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.