Pipelex Extension
Define, compose, and run AI methods in .mthds files — with full TOML support
A VS Code and Cursor extension that brings first-class editing support for MTHDS files and TOML. Rich syntax highlighting, semantic tokens, formatting, schema validation, completions, and more — built on Taplo and tracking upstream.
What is MTHDS? — An open standard for defining AI methods as typed, composable, human-readable files. A .mthds file describes what an AI should do — its inputs, outputs, logic, and data types — in plain TOML that both people and machines can read. Pipelex is the runtime that executes them. Learn more at docs.pipelex.com.
🚀 MTHDS Language Support
Context-aware highlighting and semantic tokens for every MTHDS construct — concepts, pipes, typed inputs and outputs, model references, Jinja2 templates, data injection, and more. Each construct gets its own distinct color so you can read a .mthds file at a glance.
domain = "hr_screening"
description = "Analyze a job offer to build a scorecard, batch process CVs"
main_pipe = "screen_candidates"
[concept.Scorecard]
description = "Evaluation scorecard built from a job offer"
[concept.Scorecard.structure]
job_title = { type = "text", required = true }
company = { type = "text" }
required_skills = { type = "list", item_type = "text" }
criteria = { type = "list", item_type = "concept", item_concept_ref = "hr_screening.Criterion" }
[pipe.screen_candidates]
type = "PipeSequence"
inputs = { job_offer = "Document", cvs = "Document[]" }
output = "CvResult[]"
steps = [
{ pipe = "extract_job_offer", result = "job_pages" },
{ pipe = "build_scorecard", result = "scorecard" },
{ pipe = "evaluate_cv", batch_over = "cvs", result = "results" },
]
[pipe.build_scorecard]
type = "PipeLLM"
inputs = { job_pages = "Page[]" }
output = "Scorecard"
model = "claude-4.6-opus"
prompt = """Analyze this job offer and build a scorecard..."""
See the MTHDS language reference for the full standard.
🔧 Full TOML Support
Beyond MTHDS, this extension replaces your TOML extension with complete language support — formatting, completions, hover documentation, go-to-definition, rename, diagnostics, schema validation via JSON Schema Store.
⚙️ Configuration
The extension looks for a settings file at .pipelex/plxt.toml (preferred) or plxt.toml in your project root. The format is the same as a standard Taplo configuration file — use it to configure formatting rules, schema associations, and linting options for both .mthds and .toml files.
Method validation
On every save, the extension validates your method on the hosted Pipelex API at https://api.pipelex.com, and reports the errors in the Problems panel and in the method graph. There is nothing to install and no setting to change: an API key is the only setup step (see Installation below). Before the first validation, the extension asks once for your consent to send the .mthds files in the saved file's directory.
- Use your own server: point
pipelex.api.baseUrl at a self-hosted pipelex-api, such as http://localhost:8081.
- Validate locally: set
pipelex.backend to cli to validate with a local pipelex-agent, so nothing leaves your machine.
📦 Installation
- Extensions marketplace — Search for "Pipelex" in the Extensions view
- Command line —
code --install-extension Pipelex.pipelex or cursor --install-extension Pipelex.pipelex
- Manual — Download
.vsix from releases
Then, to validate your methods, get an API key at app.pipelex.com and store it with the Pipelex: Set Hosted API Key command. The key is kept in VS Code's secret storage. When no key is stored, the extension uses the PIPELEX_API_KEY environment variable if it is set.
"Pipelex" is a trademark of Evotis S.A.S.