mcp-postman-runner
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_foldersA | List the folders in a Postman collection (name, id, path, request count). Use to confirm the folder created for a Jira ticket before running it. |
| preview_requestsA | Resolve variables for a folder or single request without executing HTTP calls. Returns redacted URLs, headers, body mode/preview, method counts, write-request count, and warnings. Use this before run_folder/run_request to confirm targets, auth scope, and write-method safety. |
| run_folderA | Execute every request in a collection folder and return structured results. Resolves {{variables}}, runs the collection + item pre-request scripts (so token auth works), fires each request, and evaluates the embedded pm.test scripts. Target the folder by folderName (typically the Jira ticket key, e.g. 'JIRA-12345') or folderId. |
| run_requestA | Execute a single named request (optionally scoped to a folder) and return its structured result. Useful for re-running one failing test case. |
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 4 tools
Each tool has a clearly distinct purpose: listing folders, previewing without execution, running a folder, and running a single request. The overlap between folder and request scoping is handled by explicit tool names and descriptions, so no ambiguity remains.
All four tool names follow the consistent verb_noun pattern (list_folders, preview_requests, run_folder, run_request) using lowercase with underscores. This makes the tool set predictable and easy to navigate.
Four tools is well-scoped for a Postman runner server. Each tool covers a necessary step in the workflow: discover, preview, execute folder, execute single request, without unnecessary additions.
The tool surface fully covers the domain of running Postman collections: listing folders to identify targets, previewing to verify safety, executing whole folders, and re-running individual requests. No obvious missing operations or dead ends.