Skip to content

Commit 6ed1bf1

Browse files
chore(mcp): add Postman MCP server stdio config and demo
1 parent 3767b9f commit 6ed1bf1

2 files changed

Lines changed: 61 additions & 0 deletions

File tree

.vscode/mcp.json

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
{
2+
"servers": {
3+
"postman": {
4+
"type": "stdio",
5+
"command": "npx",
6+
"args": [
7+
"-y",
8+
"@postman/postman-mcp-server",
9+
"--minimal",
10+
"--region us"
11+
],
12+
"env": {
13+
"POSTMAN_API_KEY": "${input:postman-api-key}"
14+
}
15+
}
16+
},
17+
"inputs": [
18+
{
19+
"id": "postman-api-key",
20+
"type": "promptString",
21+
"description": "Enter your Postman API key"
22+
}
23+
]
24+
}

MCP_POSTMAN_DEMO.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Postman MCP Server (local) — setup + demo
2+
3+
This repo includes an MCP configuration for the **Postman MCP Server** using **stdio** transport.
4+
5+
## 1) Configure Postman API key
6+
7+
The MCP server requires `POSTMAN_API_KEY`.
8+
9+
Your MCP host (VS Code / other MCP host) should prompt for the input defined in `.vscode/mcp.json`.
10+
11+
If your MCP host supports env vars directly, you can also set:
12+
13+
```bash
14+
export POSTMAN_API_KEY="<YOUR_POSTMAN_API_KEY>"
15+
```
16+
17+
## 2) Start the MCP server
18+
19+
The server is started by your MCP host using the configuration in:
20+
21+
- `.vscode/mcp.json`
22+
23+
It uses:
24+
- `npx -y @postman/postman-mcp-server --minimal --region us`
25+
26+
## 3) Demonstrate a tool capability
27+
28+
Once the MCP host is connected and the server is running, call (tool name in Postman MCP v2.x):
29+
30+
- `getWorkspaces`
31+
32+
Expected: JSON listing workspaces you have access to.
33+
34+
## Notes
35+
36+
- This configuration uses **minimal** tool set to keep startup time low.
37+
- To enable more tools, update the MCP server args from `--minimal` to `--full`.

0 commit comments

Comments
 (0)