MCP server wrapper for Postman — manage Postman workspaces, collections, environments, and APIs from your AI assistant.
Postman MCP Server (the official @postman/postman-mcp-server package) gives AI assistants access to your Postman account — browse workspaces and collections, inspect API definitions, retrieve environment variables, list team members, and navigate your entire API development workflow without leaving the chat. It connects to the Postman API using your personal API key. See postmanlabs/postman-mcp-server for full documentation.
API key required — generate at Postman API Keys.
Summary. Postman MCP Server — Dockerized from upstream @postman/postman-mcp-server package.
| Tool | Description |
|---|---|
createCollection | Createcollection |
createCollectionRequest | Createcollectionrequest |
createCollectionResponse | Createcollectionresponse |
createEnvironment | Createenvironment |
createMock | Createmock |
createSpec | Createspec |
createSpecFile | Createspecfile |
createWorkspace | Createworkspace |
duplicateCollection | Duplicatecollection |
generateCollection | Generatecollection |
generateSpecFromCollection | Generatespecfromcollection |
getAllSpecs | Getallspecs |
getAuthenticatedUser | Getauthenticateduser |
getCollection | Getcollection |
getCollections | Getcollections |
getDuplicateCollectionTaskStatus | Getduplicatecollectiontaskstatus |
getEnabledTools | Getenabledtools |
getEnvironment | Getenvironment |
getEnvironments | Getenvironments |
getGeneratedCollectionSpecs | Getgeneratedcollectionspecs |
getMock | Getmock |
getMocks | Getmocks |
getSpec | Getspec |
getSpecCollections | Getspeccollections |
getSpecDefinition | Getspecdefinition |
getSpecFile | Getspecfile |
getSpecFiles | Getspecfiles |
getTaggedEntities | Gettaggedentities |
getWorkspace | Getworkspace |
getWorkspaces | Getworkspaces |
publishMock | Publishmock |
putCollection | Putcollection |
putEnvironment | Putenvironment |
runCollection | Runcollection |
searchPostmanElements | Searchpostmanelements |
syncCollectionWithSpec | Synccollectionwithspec |
syncSpecWithCollection | Syncspecwithcollection |
updateCollectionRequest | Updatecollectionrequest |
updateMock | Updatemock |
updateSpecFile | Updatespecfile |
updateSpecProperties | Updatespecproperties |
updateWorkspace | Updateworkspace |
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
docker-compose up -d
docker run -i --rm \
-e POSTMAN_API_KEY \
hackerdogs/postman-mcp:latest
docker run -d -p 8658:8658 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8658 \
-e POSTMAN_API_KEY \
hackerdogs/postman-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"postman-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"-e",
"POSTMAN_API_KEY",
"hackerdogs/postman-mcp:latest"
],
"env": {
"MCP_TRANSPORT": "stdio",
"POSTMAN_API_KEY": ""
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"postman-mcp": {
"url": "http://localhost:8658/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8658 | HTTP port (only used with streamable-http) |
POSTMAN_API_KEY | — | Postman API key — generate at postman.co/settings/me/api-keys |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly. If you don't specify, Hackerdogs will automatically choose the best tool for the job.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/postman-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name postman-mcp-test -p 8658:8658 \
-e MCP_TRANSPORT=streamable-http \
-e POSTMAN_API_KEY \
hackerdogs/postman-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8658/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8658/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. List available tools:
curl -s -X POST http://localhost:8658/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'
4. Clean up:
docker stop postman-mcp-test
Content type
Image
Digest
sha256:9ab7610f5…
Size
106.9 MB
Last updated
3 months ago
docker pull hackerdogs/postman-mcp