zod-contract-mock-forge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| introspect_schemaA | Convert a Zod schema string to JSON Schema for LLM understanding. Use to answer: what is the structure and constraints of this schema? |
| read_schema_from_fileA | Read a Zod schema directly from a TypeScript or JavaScript file. Use to answer: what schema is defined in this file? |
| generate_valid_mockA | Generate valid mock data from a Zod schema string. Use to answer: what does a valid payload for this schema look like? |
| generate_boundary_violationsA | Generate intentionally invalid payloads based on a Zod schema — for negative testing. Use to answer: what invalid inputs should I test against this API? |
| generate_exhaustive_union_violationsA | Generate violation payloads for every branch of a z.union() or z.discriminatedUnion() schema. Use when generate_boundary_violations only covers one union variant and you need full branch coverage. |
| generate_mock_variantsA | Generate N structurally valid but value-diverse mocks from a Zod schema — for property-based testing. Use when generate_valid_mock is too deterministic and you need varied inputs to surface edge cases. Supply seed for reproducible output in CI. |
| scaffold_api_contract_testA | Generate an API contract test or mock boilerplate for Playwright, Jest, Vitest, or MSW. Use to answer: how do I write a test that validates this API endpoint against this schema? |
| suggest_contract_fixA | Validate a JSON payload against a Zod schema and suggest fixes for each violation. Use to answer: why does this payload fail validation, and how do I fix it? |
| detect_schema_driftA | Compare a Zod schema in a TypeScript file against an OpenAPI spec — finds silent divergence. Use when Zod and OpenAPI docs are maintained separately and may have drifted apart. Reports missing fields, extra fields, type conflicts, and required/optional mismatches. |
| evaluate_schema_evolutionA | Detect breaking changes when a Zod schema is tightened — before tests run. Generates mocks from the old schema, validates them against the new schema, and reports exactly which fields and constraints now reject previously valid data. Use when you changed a schema and want to know if existing test fixtures will break. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation on Zod schemas: reading, introspecting, generating various mocks, testing, fixing, and comparing. No two tools have overlapping purposes.
All tool names use a consistent verb_noun pattern in snake_case, making the set predictable and easy to navigate.
With 10 tools, the server is well-scoped for its purpose—covering schema analysis, mock generation, testing, and validation without being overwhelming or sparse.
The tool set covers the full workflow: reading schemas, understanding their structure, generating valid/invalid mocks, creating tests, suggesting fixes, and tracking changes. No obvious gaps.