Tdcv2

What tdcv2 does

The tdcv2 MCP server gives coding agents an interface to the TDCv2 test-data engine. An agent can create a small .tdc configuration, validate it, and ask the engine to generate rows on the local machine. Running the same configuration produces the same output byte for byte, making the generated fixture reproducible.

Output can be CSV, JSON, SQL inserts, or another text format supported by the configuration. TDCv2 configurations can describe fields that depend on one another, exact shares, related tables, and data packs covering 95 languages and 198 countries. The repository also contains a skill that teaches an agent the TDC language and the recommended workflow.

How it works

The tdcv2 MCP server runs as a local Node.js process and invokes the TDCv2 engine. The agent can begin with a request such as generating customers from multiple countries or producing distinct users for a test. It then writes the corresponding configuration, checks that configuration with the engine, generates the requested file, and can provide the configuration needed to reproduce it.

The server reads .tdc files and writes generated files only within the project directory where it starts. The engine and server do not send project data or configurations to a remote service during normal local operation. Network activity can still occur when npx downloads the pinned package versions, when data packs are added, or when a configuration explicitly uses an HTTP generator.

This release is checked against TDCv2 engine version 0.3.3. If another engine version is used, its documentation may be read, and that engine's own configuration check determines validity.

Setup and configuration

Node.js 20 or newer is required. For a general MCP client, register the server with a stdio configuration that runs npx -y tdcv2-mcp@0.1.2. On Windows, use npx.cmd if the client cannot launch npx directly.

Claude Code can install the repository plugin, which includes both the skill and the server. Agents that read skills can install the skill with the package's install-skill command, targeting a user, agent, project, or custom skills directory. The MCP server itself does not require environment variables according to the provided setup instructions.

Tools and capabilities

The tdcv2 MCP server exposes tools for:

• Checking a .tdc configuration with the engine.
• Generating test-data files from a configuration.
• Finding or managing available data packs through the documented pack workflow.
• Summarising an existing generated file.
• Reading TDCv2 documentation.

The associated skill is a separate part of the package. It helps an agent understand the TDC language, the generation process, and common configuration pitfalls, while the MCP tools provide the executable operations.

Limitations and notes

Generation is local and scoped to the server's starting project folder. The package installation uses npx, so the first start may download the specified server package and its dependencies from npm. Data packs are downloaded only when the pack-add operation is requested. A configuration containing an HTTP generator can send its named values to the configured URL; this is an explicit behavior of that configuration, not a default server action.

The package version in the documented commands is 0.1.2, and it is checked against TDCv2 0.3.3. Different versions may have different documentation or behavior. The project is licensed under MIT.