Ext Ops Panel
Open dashboard
Comparison

Webflow vs Postman MCP Server

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-15. 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
MarketplaceWebflowPostman MCP Server
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 36
Pulls (Docker Hub): 17 482
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Listed
Version: sha256:73f715030cbe
Forks (GitHub): 87
Pulls (Docker Hub): 45 216
Stars (Docker Hub): 6
Stars (GitHub): 319
Not marked · First seen
Official MCP Registry Not listed 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

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

Webflow vs Postman MCP Server
FactWebflowPostman MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)141 (worse)319 (better)
Pulls (Docker Hub) (differs)17 482 (worse)45 216 (better)
Forks (GitHub) (differs)36 (worse)87 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/webflow)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)2142
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITApache-2.0
Repository (differs)github.com/webflow/mcp-servergithub.com/postmanlabs/postman-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Webflow

In its own words, on Docker MCP Catalog:

Model Context Protocol (MCP) server for the Webflow Data API.

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

Webflow As a local MCP server: Docker image

Claude Code
claude mcp add --env "WEBFLOW_TOKEN=<YOUR_WEBFLOW_TOKEN>" --transport stdio webflow -- docker run -i --rm -e WEBFLOW_TOKEN mcp/webflow

Requires: WEBFLOW_TOKEN (secret)

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.

Tools each declares

Only Webflow declares

  • collection_fields_create_option
  • collection_fields_create_reference
  • collection_fields_create_static
  • collection_fields_update
  • collections_create
  • collections_get
  • collections_items_create_item
  • collections_items_create_item_live
  • collections_items_list_items
  • collections_items_publish_items
  • collections_items_update_items
  • collections_items_update_items_live
Show the remaining 9
  • collections_list
  • pages_get_content
  • pages_get_metadata
  • pages_list
  • pages_update_page_settings
  • pages_update_static_content
  • sites_get
  • sites_list
  • sites_publish

Only Postman MCP Server declares

  • createCollection
  • createCollectionRequest
  • createCollectionResponse
  • createEnvironment
  • createMock
  • createSpec
  • createSpecFile
  • createWorkspace
  • duplicateCollection
  • generateCollection
  • generateSpecFromCollection
  • getAllSpecs
Show the remaining 30
  • getAuthenticatedUser
  • getCollection
  • getCollections
  • getDuplicateCollectionTaskStatus
  • getEnabledTools
  • getEnvironment
  • getEnvironments
  • getGeneratedCollectionSpecs
  • getMock
  • getMocks
  • getSpec
  • getSpecCollections
  • getSpecDefinition
  • getSpecFile
  • getSpecFiles
  • getTaggedEntities
  • getWorkspace
  • getWorkspaces
  • publishMock
  • putCollection
  • putEnvironment
  • runCollection
  • searchPostmanElements
  • syncCollectionWithSpec
  • syncSpecWithCollection
  • updateCollectionRequest
  • updateMock
  • updateSpecFile
  • updateSpecProperties
  • updateWorkspace

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Webflow asks for

  • WEBFLOW_TOKEN (secret)

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: Webflow · What it can do: Postman MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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