Postman MCP Server vs GitLab MCP Server
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)). GitLab MCP Server is an MCP server published by zereight. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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 |  GitLab MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 2.15.0 Downloads/month (npm): 46 496 Downloads/week (npm): 7 759 Forks (GitHub): 86 Stars (GitHub): 329 Not marked · First seen |
Listed Version: 2.3.26 Downloads/month (npm): 557 520 Downloads/week (npm): 190 479 Forks (GitHub): 369 Stars (GitHub): 2 100 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:73f715030cbe Forks (GitHub): 86 Pulls (Docker Hub): 47 610 Stars (Docker Hub): 6 Stars (GitHub): 329 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 2.15.0 Downloads/month (npm): 46 496 Downloads/week (npm): 7 759 Forks (GitHub): 86 Stars (GitHub): 329 Not marked · First seen |
Listed Version: 2.3.26 Downloads/month (npm): 557 520 Downloads/week (npm): 190 479 Forks (GitHub): 369 Stars (GitHub): 2 100 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 | Postman MCP Server | GitLab MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 329 (worse) | 2 100 (better) |
| Pulls (Docker Hub) (differs) | 47 610 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 86 (worse) | 369 (better) |
| Last release (differs) | 2026-10-30 (worse) | 2026-11-12 (better) |
| Where it runs (differs) | Remote server or your machine | On your machine (@zereight/mcp-gitlab) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 21, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/postmanlabs/postman-mcp-server | github.com/zereight/gitlab-mcp |
| Changes in the last 7 days (differs) | 0 | 7 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 16 h ago, requires authentication | no 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
Give your AI agents trusted access to the full Postman platform.
GitLab MCP Server
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
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
GitLab MCP Server As a local MCP server: npm package
claude mcp add --env "GITLAB_JOB_TOKEN=<YOUR_GITLAB_JOB_TOKEN>" --env "GITLAB_PERSONAL_ACCESS_TOKEN=<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>" --transport stdio gitlab-mcp -- npx -y @zereight/mcp-gitlabRequires: GITLAB_JOB_TOKEN (secret), GITLAB_PERSONAL_ACCESS_TOKEN (secret)
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 GitLab MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only Postman MCP Server asks for
POSTMAN_API_KEY (secret)
Only GitLab MCP Server asks for
GITLAB_ALLOWED_PROJECT_IDSGITLAB_API_URLGITLAB_AUTH_COOKIE_PATHGITLAB_CA_CERT_PATHGITLAB_DENIED_TOOLS_REGEXGITLAB_JOB_TOKEN (secret)GITLAB_MASKING_CONFIGGITLAB_MASKING_ENABLEDGITLAB_MASKING_POLICY_FILEGITLAB_MASKING_WORKSPACE_DIRGITLAB_OAUTH_CLIENT_IDGITLAB_OAUTH_TOKEN_SCRIPT
Show the remaining 9
GITLAB_PERMISSION_MODEGITLAB_PERSONAL_ACCESS_TOKEN (secret)GITLAB_PERSONAL_ACCESS_TOKEN_FILEGITLAB_TOOLSGITLAB_TOOLSETSGITLAB_TOOL_POLICY_APPROVEGITLAB_TOOL_POLICY_HIDDENGITLAB_USE_OAUTHNODE_TLS_REJECT_UNAUTHORIZED
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: GitLab MCP Server · 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.