mcpField
T
Triplex schema contracts

Triplex schema contracts

Local
triplexanalytics.ioDeveloper Tools0Updated 6d ago
RepositoryVisit website

About Triplex schema contracts

A local, read-only MCP server for coding agents and other MCP clients to infer and validate schema contracts in CSV, TSV, and JSON Lines files. It runs over stdio without network access.

Key features

  1. 01Infer contracts from local files
  2. 02Validate files against `.triplex.yaml`
  3. 03Support CSV, TSV, and JSON Lines
  4. 04Read-only local file access
  5. 05Stdio JSON-RPC transport

Use cases

  1. 01Infer a contract for a data file
  2. 02Check a file against an existing contract

MCP support

Exposes `schema_infer` and `schema_validate` tools to MCP clients over stdio. Both operate on local file paths and do not access the network.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
cargotriplex-mcp0.48.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

triplex-mcp

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-mcp
triplex-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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.