Triplex schema contracts
io.github.triplexanalyticsPublished by GitHub account triplexanalyticsv0.48.1Updated Nov 6, 2026
Infer and validate schema contracts on local CSV, TSV and JSON Lines files. No network access.
Overview
Local stdio MCP server that lets an assistant infer and validate schema contracts for local CSV, TSV and JSON Lines files.
- What you can do
- Infer a schema contract from a local CSV, TSV or JSON Lines file, optionally sampling a limited number of rows.
- Validate a local data file against an existing .triplex.yaml schema contract.
- Both tools are read-only and work only on local file paths; no anonymization tool is exposed yet.
- When to use it
- Useful when a coding agent needs to profile a local tabular or JSON Lines dataset, draft a schema contract for it, or check that a file still matches an agreed contract before downstream work.
- Requirements
- Runs as a local process over stdio, installed with cargo install triplex-mcp (Rust/Cargo toolchain). No flags, config file, network access, accounts or credentials. The MCP client's stdio transport must point at the binary.
Installation
In SourceWeft
- Open Triplex schema contracts in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.yamlcontract (triplex_schemacast::validate_path).
Both are read-only and take a local file path. anonymize isn't exposed
yet.
Run
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
Source: apps/triplex-mcp/README.md at commit 0d0881b
Tools
0Version history
1- v0.48.1LatestOct 23, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts