MCP

Synth speaks MCP, so an assistant can generate and check data without shelling out to the CLI:

go install github.com/bakhod1r/synth/mcp/cmd/synth-mcp@latest
claude mcp add synth -- synth-mcp

Eight tools: generate, list_types, list_presets, verify, profile, mask, snapshot, diff.

Why it takes arguments, not paths

The server is stdio-only and takes every input as an argument rather than a path — it opens no socket and reads no file, and a test forbids the imports that would let it. An MCP server runs with your permissions on behalf of a model that may be reading text someone else wrote, so a path argument would turn a data generator into a file-reading primitive.

flowchart LR
  M["Assistant"] <-->|"stdio<br/>JSON-RPC"| S["synth-mcp"]
  S --> E["Synth engine"]
  E --> S
  S -.->|"blocked by a test"| F["filesystem"]
  S -.->|"blocked by a test"| N["network"]
  S -.->|"never existed"| D["database"]

  style F stroke-dasharray: 4, color:#888
  style N stroke-dasharray: 4, color:#888
  style D stroke-dasharray: 4, color:#888

Data goes in as an argument and comes back in the response. Nothing else moves.

A separate module

mcp-go brings 20 transitive dependencies, kept out of the core module's graph.

Full detail: mcp/README.md.