mcp-mock

# mcp-mock mcp-mock is a lightweight synthetic mock server for the Model Context Protocol (MCP). It is designed for local testing, demos, and resilience experiments where you want a predictable MCP endpoint without depending on a real backend. The current codebase includes: - a `MockMCPServer` implementation for registering tools and serving responses - a synthetic response generator powered by Faker - a chaos layer for latency and injected failures - a CLI entry point for running a mock server from a schema file - a pytest suite covering the core behaviors ## Project layout ```text mcp-mock/ ├── pyproject.toml ├── README.md ├── LICENSE ├── src/ │ └── mcp_mock/ │ ├── __init__.py │ ├── chaos.py │ ├── cli.py │ ├── generator.py │ └── server.py └── tests/ ├── test_chaos.py ├── test_cli.py ├── test_generator.py └── test_server.py ``` ## Installation Install the package from the project root: ```bash python -m pip install -e . ``` Install development dependencies as well: ```bash python -m pip install -e ".[dev]" ``` ## Usage mcp-mock is most useful when you want a predictable MCP server for local development, test automation, or demos. You can either run it from the command line with a schema file or create a server directly in Python. ### CLI usage The CLI entry point is `mcp-mock serve`. It reads a JSON file that describes the tools you want to expose and starts a mock MCP server over stdio. Run a server from a schema file: ```bash mcp-mock serve --schema ./tools_schema.json ``` Add simulated latency and failure injection: ```bash mcp-mock serve --schema ./tools_schema.json --latency 100 --error-rate 0.1 ``` #### CLI options - `--schema` or `-s`: required path to a JSON schema file - `--latency`: adds a delay in milliseconds before each tool response - `--error-rate`: injects failures probabilistically, from `0.0` to `1.0` ### Python API usage You can also create a server programmatically in Python.…