Who is this for?
- MCP Server Developers - Test your tools work correctly with real LLMs
- MCP Client Developers - Build robust multi-server applications
- App Marketplace Maintainers - Evaluate server quality and compatibility
- SDK Developers - Integrate MCP capabilities into your products
What can you do with it?
Unit Testing
Test MCP primitives (tools, resources, prompts) deterministically without LLM calls
End-to-End Testing
Simulate real user interactions by connecting LLMs to your MCP servers
toConformanceReport(...) and renderConformanceReportJUnitXml(...).
Installation
Quick Example
Renames in 1.11.
TestAgent → HostRunner, EvalAgent → HostExecutor, .prompt() → .run(), Host.addServer() → Host.requireServer(). No deprecation aliases. The same code with the old names will not type-check against @mcpjam/sdk@>=1.11.Spec-first: Host + HostRuntime
For richer setups — pinning a host style/profile, applying sandbox/permission policy, or running the same configuration in CI that the MCPJam Inspector uses — start from a Host spec instead of constructing a runner directly:

