Sign inSign up

hackerdogs/postman-mcp

By hackerdogs

•Updated 3 months ago

Postman MCP Server

Image
0

234

hackerdogs/postman-mcp repository overview

Hackerdogs
hackerdogs ⁠

⁠Postman MCP Server

MCP server wrapper for Postman⁠ — manage Postman workspaces, collections, environments, and APIs from your AI assistant.

⁠What is Postman?

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.

⁠Tools Reference

ToolDescription
createCollectionCreatecollection
createCollectionRequestCreatecollectionrequest
createCollectionResponseCreatecollectionresponse
createEnvironmentCreateenvironment
createMockCreatemock
createSpecCreatespec
createSpecFileCreatespecfile
createWorkspaceCreateworkspace
duplicateCollectionDuplicatecollection
generateCollectionGeneratecollection
generateSpecFromCollectionGeneratespecfromcollection
getAllSpecsGetallspecs
getAuthenticatedUserGetauthenticateduser
getCollectionGetcollection
getCollectionsGetcollections
getDuplicateCollectionTaskStatusGetduplicatecollectiontaskstatus
getEnabledToolsGetenabledtools
getEnvironmentGetenvironment
getEnvironmentsGetenvironments
getGeneratedCollectionSpecsGetgeneratedcollectionspecs
getMockGetmock
getMocksGetmocks
getSpecGetspec
getSpecCollectionsGetspeccollections
getSpecDefinitionGetspecdefinition
getSpecFileGetspecfile
getSpecFilesGetspecfiles
getTaggedEntitiesGettaggedentities
getWorkspaceGetworkspace
getWorkspacesGetworkspaces
publishMockPublishmock
putCollectionPutcollection
putEnvironmentPutenvironment
runCollectionRuncollection
searchPostmanElementsSearchpostmanelements
syncCollectionWithSpecSynccollectionwithspec
syncSpecWithCollectionSyncspecwithcollection
updateCollectionRequestUpdatecollectionrequest
updateMockUpdatemock
updateSpecFileUpdatespecfile
updateSpecPropertiesUpdatespecproperties
updateWorkspaceUpdateworkspace

⁠Example Prompts

Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:

  • "List all my Postman workspaces and their types (personal, team, public)."
  • "Show me all collections in the 'Backend Services' workspace and their request counts."
  • "Get the environment variables defined in the 'Production' Postman environment."
  • "Find all API endpoints in the 'Auth Service' collection that use POST and return their paths."
  • "List my Postman team members and their roles."
  • "Show the OpenAPI/Swagger definition for the 'Payments API' in my Postman workspace."

⁠Deploy

docker-compose up -d
⁠Docker Run (stdio mode)
docker run -i --rm \
  -e POSTMAN_API_KEY \
  hackerdogs/postman-mcp:latest
⁠Docker Run (HTTP streamable mode)
docker run -d -p 8658:8658 \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_PORT=8658 \
  -e POSTMAN_API_KEY \
  hackerdogs/postman-mcp:latest

⁠MCP Client Configuration

⁠Stdio mode (default)

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": ""
      }
    }
  }
}
⁠HTTP mode (streamable-http)

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.

⁠Environment Variables

VariableDefaultDescription
MCP_TRANSPORTstdioTransport mode: stdio or streamable-http
MCP_PORT8658HTTP port (only used with streamable-http)
POSTMAN_API_KEY—Postman API key — generate at postman.co/settings/me/api-keys⁠

⁠Installing in Hackerdogs

The fastest way to get started is through Hackerdogs⁠:

  1. Log in to your Hackerdogs account.
  2. Go to the Tools Catalog.
  3. Search for the tool by name.
  4. Expand the tool card and click Install — you're ready to go.

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.

  1. Vendor API key required? Add your key in the config environment variable field before clicking Install. Your key will be encrypted at rest.
  2. Enable / Disable the tool anytime from the Enabled Tools page.
  3. Need to update a key or parameter? Go to My Tools → toggle Show Decrypted Values → edit → Save.

Want to contribute or chat with the team? Join our Discord⁠.

⁠Build

docker build -t hackerdogs/postman-mcp:latest .

⁠Testing

⁠Automated tests
./test.sh
⁠Test directly with Docker

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

Tag summary

Content type

Image

Digest

sha256:9ab7610f5…

Size

106.9 MB

Last updated

3 months ago

docker pull hackerdogs/postman-mcp