A generic MCP server for executing Postman collections — supports v2.1 collections, environments, variable chaining, and scripting
A generic MCP server for executing Postman collections — supports v2.1 collections, environments, variable chaining, and scripting. Exposed over MCP by the postman mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A full-featured Model Context Protocol (MCP) server for executing Postman collections using Python. Enables AI assistants to run, inspect, and manage API test workflows from any Postman v2.1 collection file — with a strict, safe execution pipeline that never guesses credentials.
Everything the assistant can do here goes through one of these:
prepare_collection — Validates collection + scans variables + generates config file for user to fillrun_collection — Executes a collection after validating all requirements are metinspect_collection — View collection metadata, folders, and request listingdry_run_collection — Preview resolved URLs without making HTTP callscheck_status — Check if a collection is ready to execute (config filled?)list_collections — Scan a directory for available collection filesmcp[cli] package (FastMCP framework) - No additional dependencies for core features (uses stdlib http.client) - Optional: dukpy for full JavaScript execution engineInstallation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Postman's toolset — prepare_collection, run_collection, inspect_collection and 3 more — is a fair guide to whether it matches your workflow.
This entry was verified against Postman's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| prepare_collection | Validates collection + scans variables + generates config file for user to fill |
| run_collection | Executes a collection after validating all requirements are met |
| inspect_collection | View collection metadata, folders, and request listing |
| dry_run_collection | Preview resolved URLs without making HTTP calls |
| check_status | Check if a collection is ready to execute (config filled?) |
| list_collections | Scan a directory for available collection files |
{
"mcpServers": {
"postman-runner": {
"command": "uvx",
"args": ["postman-runner-mcp"],
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
mcp[cli] package (FastMCP framework) - No additional dependencies for core features (uses stdlib http.client) - Optional: dukpy for full JavaScript execution engineScoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.