Triplex schema contracts

triplex-mcp

[Triplex schema contracts MCP server]

MCP (Model Context Protocol) server over SchemaCast, stdio transport only. A coding agent (Claude Code or any other MCP client) launches this as a local process and talks to it over its own stdin/stdout, same trust boundary as apps/triplex-cli: no network, no server, nothing here reads bytes over the wire.

Tools

• schema_infer(path, sample_rows?): infers a schema contract from a local file (triplex_schemacast::infer_schema_from_path).
• schema_validate(schema_path, input_path, sample_rows?): checks a local file against a .triplex.yaml contract (triplex_schemacast::validate_path).

Both are read-only and take a local file path. anonymize isn't exposed yet.

Run

cargo install triplex-mcptriplex-mcp

From a checkout of this repository: cargo run -p triplex-mcp.

Speaks newline-delimited JSON-RPC 2.0 on stdin/stdout. Point an MCP client's stdio transport at this binary. No flags, no config file.

Build/test

Ordinary workspace crate: cargo build -p triplex-mcp, cargo test -p triplex-mcp, cargo clippy -p triplex-mcp --all-targets. Covered by the root cargo test --workspace/CI already; there is no separate Makefile target.

MCP registry

The official MCP registry lists servers by name and points MCP clients to the package to install; for this server, that package is this crate on crates.io. The registry confirms that the crate belongs to the entry by reading the line below in the published README, so it has to stay:

mcp-name: io.github.triplexanalytics/triplex-mcp