Postman MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-collectionC | Run a Postman Collection using Newman |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The naming follows a clear verb_noun pattern.
A single tool is too few for a server named 'Postman MCP Server', which suggests broader Postman API functionality. This minimal set feels thin and under-scoped for the implied domain.
The tool surface is severely incomplete for a Postman server. It only allows running collections, missing essential operations like creating/editing collections, managing environments, viewing results, or interacting with other Postman features.