Mcpclientmock

Wraps James Bloom's MockServer in an MCP interface so you can create HTTP expectations, verify request patterns, and manage mock state through natural language. Exposes operations for setting up request/response pairs with matchers for method, path, headers, and body, plus verification tools to confirm your app made the calls you expected. Useful when you're building against APIs that don't exist yet or need reproducible test scenarios without spinning up real services. Connects to any MockServer instance over configurable host and port. Think of it as programmatic control over your HTTP mocks, but driven by conversation instead of REST calls or configuration files.