MIT
Postman MCP Server
by shannonlal
Postman MCP 서버
Newman을 사용하여 Postman 컬렉션을 실행할 수 있는 MCP(Model Context Protocol) 서버입니다. 이 서버를 통해 LLM은 API 테스트를 실행하고 표준화된 인터페이스를 통해 자세한 결과를 얻을 수 있습니다.
특징
Newman을 사용하여 Postman 컬렉션 실행
환경 파일 지원
전역 변수 지원
다음을 포함한 자세한 테스트 결과:
전반적인 성공/실패 상태
시험 요약(전체, 합격, 불합격)
자세한 실패 정보
실행 타이밍
Related MCP server: Postman MCP Server
설치
Smithery를 통해 설치
Smithery 를 통해 Claude Desktop용 Postman Runner를 자동으로 설치하려면:
지엑스피1
수동 설치
# Clone the repository
git clone <repository-url>
cd mcp-postman
# Install dependencies
pnpm install
# Build the project
pnpm build용법
구성
~/Library/Application Support/Claude/claude_desktop_config.json 에 있는 Claude 데스크톱 구성 파일에 서버를 추가합니다.
{
"mcpServers": {
"postman-runner": {
"command": "node",
"args": ["/absolute/path/to/mcp-postman/build/index.js"]
}
}
}사용 가능한 도구
런 컬렉션
Postman 컬렉션을 실행하고 테스트 결과를 반환합니다.
매개변수:
collection(필수): Postman 컬렉션에 대한 경로 또는 URLenvironment(선택 사항): 환경 파일의 경로 또는 URLglobals(선택 사항): globals 파일에 대한 경로 또는 URLiterationCount(선택 사항): 실행할 반복 횟수
응답 예시:
{
"success": true,
"summary": {
"total": 5,
"failed": 0,
"passed": 5
},
"failures": [],
"timings": {
"started": "2024-03-14T10:00:00.000Z",
"completed": "2024-03-14T10:00:01.000Z",
"duration": 1000
}
}Claude에서의 사용 예
Claude에서 Postman 컬렉션을 실행하도록 요청하여 서버를 사용할 수 있습니다.
"/path/to/collection.json에서 Postman 컬렉션을 실행하고 모든 테스트가 통과되었는지 알려주세요"
클로드는 다음을 할 것입니다:
실행 수집 도구를 사용하세요
테스트 결과를 분석하다
실행에 대한 인간 친화적인 요약을 제공합니다.
개발
프로젝트 구조
src/
├── index.ts # Entry point
├── server/
│ ├── server.ts # MCP Server implementation
│ └── types.ts # Type definitions
└── newman/
└── runner.ts # Newman runner implementation
test/
├── server.test.ts # Server tests
├── newman-runner.test.ts # Runner tests
└── fixtures/ # Test fixtures
└── sample-collection.json테스트 실행
# Run tests
pnpm test
# Run tests with coverage
pnpm test:coverage건물
# Build the project
pnpm build
# Clean build artifacts
pnpm clean기여하다
저장소를 포크하세요
기능 브랜치를 생성합니다(
git checkout -b feature/amazing-feature)변경 사항을 커밋하세요(
git commit -m 'Add some amazing feature')브랜치에 푸시(
git push origin feature/amazing-feature)풀 리퀘스트 열기
특허
아이에스씨
Available Tools
1 toolrun-collectionC
Run a Postman Collection using Newman
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | Path or URL to the Postman collection | |
| environment | No | Optional path or URL to environment file | |
| globals | No | Optional path or URL to globals file | |
| iterationCount | No | Optional number of iterations to run |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It fails to mention critical behavioral traits such as whether this is a read-only or destructive operation, authentication requirements, rate limits, execution time, or what happens during the run (e.g., output format, error handling).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of running a Postman collection (which involves execution, potential side effects, and output), the lack of annotations and output schema means the description is incomplete. It does not address what the tool returns, error conditions, or behavioral implications, leaving significant gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, clearly documenting all four parameters. The description adds no additional semantic information about parameters beyond what the schema provides, so it meets the baseline of 3 for adequate but not additive value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Run') and the resource ('a Postman Collection using Newman'), providing a specific verb+resource combination. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without offering any usage instructions or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
run-collection
TDQS
B3.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running a Postman Collection using Newman, leaving no room for misselection.
Naming Consistency5/5
The single tool name 'run-collection' follows a clear verb-noun pattern, using a hyphen for separation. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.
Tool Count2/5
A single tool is too few for a server named 'Postman MCP Server', which suggests a broader scope related to Postman API testing. This minimal toolset feels thin and underdeveloped, limiting functionality to just running collections without supporting other common Postman operations.
Completeness2/5
The tool surface is severely incomplete for a Postman-related domain. It only covers running collections, missing obvious gaps such as creating, managing, or listing collections, environments, or variables, which are core to Postman workflows and would cause significant agent failures.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive
Related MCP Connectors
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Give your AI agents trusted access to the full Postman platform.
Direct access to Cypress tests results and accessibility reports in your AI workflow.
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables running Postman collections using Newman, allowing LLMs to execute API tests and get detailed results through a standardized interface.150 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Postman workspaces, collections, requests, responses, and monitors through the Postman API. Allows users to manage API collections, create and update requests/responses, and execute monitors directly from chat.17 npmMIT
- AlicenseBqualityDmaintenanceAutomatically generates Postman collections from code directories by analyzing API endpoints and parameters, enabling easy testing, documentation, and sharing.143MIT