MCP Server Tester는 MCP 서버의 자동화된 테스트를 위한 도구입니다.

왜 이 도구?

일관되게 작동하는 믿을 수 있는 MCP 서버를 건축하고 spec-compliant는 그것 보다는 더 단단합니다:

• Inspector 도구는 내장 서버를 구축하고 테스트하는 데 도움이되지만 회귀에서 당신을 보호하지 않습니다.
• 도구는 직접 테스트에서 완벽하게 작동하지만, LLMs는 실제 세계에서 확실히 주장하고 주장합니다.
• 대부분의 MCP SDK는 완전히 spec-compliant가 아니며 누락 된 것을 알 수 없습니다.
• spec는 급속하게 진화하고, 최선의 관행으로 현재를 체재하기 위하여 열심히

mcp-server-tester]는 이러한 핵심 문제를 해결하는 데 도움이되는 3 개의 초점을 맞춘 명령을 제공하는 구현 영역 CLI 테스트 도구입니다.

• tools - 직접 MCP 통화로 공구 작업을 올바르게 검증하는 테스트 -evals - LLM을 검증하는 실행 테스트는 지속적으로 이해하고 도구를 올바르게 사용
• compliance - 프로토콜이 진화하는 것과 같이 자동화된 서버 spec 검증 (Work in Progress)

---

명령

tools - 직접 MCP 도구 테스트

직접 API 호출과 도구를 올바르게 테스트:

** 샘플 출력 : **

evals - LLM 통합 테스트

MCP Server Tester

The MCP Server Tester is a tool for automated testing of MCP servers.

Why this tool?

Building reliable MCP servers that work consistently and are spec-compliant is harder than it should be:

• the Inspector tool helps to build and test the intial server, but won’t protect you from regressions
• tools works perfectly in direct testing, but LLMs use them incorrectly and inconsistently in the real world
• most MCP SDKs aren’t fully spec-compliant, and it’s hard to know what’s missing
• the spec evolves rapidly, making it hard to stay current with best practices

The mcp-server-tester is a implementation-agnostic CLI testing tool that provides three focused commands that help solve these core issues:

• tools - Run tests that verify your tools work correctly with direct MCP calls
• evals - Run tests that verify LLMs can consistently understand and use your tools correctly
• compliance - Automated server spec validation as the protocol evolves (Work in Progress)

---

Commands

tools - Direct MCP Tool Testing

Test your tools work correctly with direct API calls:

npx mcp-server-tester tools tool-tests.yaml --server-config filesystem-server-config.json

Sample output:

✅ Tool Discovery: Found 3 tools (read_file, write_file, delete_file)
✅ Write file successfully
✅ Read file returns content
✅ Write and read workflow
❌ Handle invalid path - Expected error containing 'permission' but got 'access denied'
✅ Delete file cleanup

Results: 5/6 tests passed

evals - LLM Integration Testing

Test that LLMs can discover and use your tools effectively:

npx mcp-server-tester evals eval-tests.yaml --server-config filesystem-server-config.json

Sample output:

🤖 Testing with claude-3-5-haiku-latest
✅ LLM can create and read files
✅ File manipulation workflow
✅ Error handling test
❌ Documentation query task: FAILED
    Prompt: "How do I search for configuration files in the project?"
    • Required tool 'search_docs' was not called (actual calls: list_files)
❌ Lists all available tools: FAILED
    Prompt: "Please list all available file management tools you have access to."
    • LLM judge failed: Score: 0.3/1.0 (threshold: 0.8). Assistant did not provide complete tool list.

Results: 3/5 tests passed

Note: Requires ANTHROPIC_API_KEY environment variable.

compliance - MCP Specification Compliance Testing (WIP)

Test that your server is spec compliant:

npx mcp-server-tester compliance --server-config filesystem-server-config.json

See the Compliance Command (WIP) section below for details and example output.

Quick Start

1. Create server config (filesystem-server-config.json):

   {
     "mcpServers": {
       "filesystem": {
         "command": "node",
         "args": ["./filesystem-server.js"]
       }
     }
   }
   

2. Create tool and eval test files manually: