Pipelex lets you build AI methods with your coding agent and run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
1. Sign up at app.pipelex.com.
2. Install the Pipelex plugin in your coding agent. The plugin gives your agent the skills that build methods, run them and put them in your software, a hook that checks every edit, and the Pipelex tools.
Claude Code
claude plugin marketplace add Pipelex/pipelex-plugins
claude plugin install pipelex@pipelex-pluginsClaude Code asks for an API key when you enable the plugin, and stores it in your OS keychain — create one in your console at app.pipelex.com. The skills, the hook that checks every edit and the Pipelex tools load with it. The plugin's hook and the Pipelex tools run on Node.js, so you need Node.js on your PATH.
Claude Code also loads what you have added to your Claude account, so if you added the Pipelex MCP to Claude, Claude Code has it too. An agent with the plugin does not need the Pipelex MCP, and there is nothing to turn off: when both are present, the Pipelex MCP defers to the plugin's tools.
Codex
codex plugin marketplace add Pipelex/pipelex-plugins
export PIPELEX_API_KEY=plx_sk_... # create one in your console at app.pipelex.comRestart Codex, run /plugins to install pipelex, and trust the plugin hook on first run. Requires Codex 0.141 or later. The plugin's hook and the Pipelex tools run on Node.js, so you need Node.js on your PATH.
3. Ask your agent for the method you want.
Design a method that reads an invoice PDF and returns the supplier, the total and the line items. Then run it on
~/Downloads/invoice.pdfand save it to my Pipelex account.
/pipelex-design writes the method, the hook checks it on every edit, /pipelex-run starts it and prints a run id you can come back to, and /pipelex-catalog saves it to your account, where your chatbot can run it too.
Run your methods from your chatbot. The Pipelex MCP is a connector for your chatbot (ChatGPT, Claude): it gives it access to the Pipelex service, so it can list the methods saved in your account and run them right in the conversation. Your methods become your chatbot's tools. To build a method, use the Pipelex plugin in a coding agent such as Claude Code or Codex, as in steps 2 and 3 above.
Add the Pipelex MCP in your chatbot's settings by the address below — in Claude, that is Add custom connector — then sign in with your Pipelex account when asked. Nothing to install and no key: the Pipelex MCP runs on your signed-in session.
https://mcp.pipelex.com/mcp
Then ask your chatbot:
What methods do I have?
Run the invoice method on https://raw.githubusercontent.com/Pipelex/pipelex-cookbook/main/assets/extract_proof_of_purchase/restaurant_invoice.pdf
You get a run id straight away, and you can ask for its status, its results or the files it produced at any time.
Give the file as a URL the Pipelex MCP can reach. In ChatGPT you can attach it to the conversation instead and ask for a run on it; Claude has no way yet to hand the Pipelex MCP a file you attached.
The other two ways, built by your agent too. Ask it for a webapp around the method, and /pipelex-scaffold creates a new app from the method-app template and leaves it running on your machine. Ask it to call the method from your TypeScript or Python code, and /pipelex-integrate generates the method's types and one typed call that runs it, through the TypeScript SDK @pipelex/sdk or the Python SDK pipelex-sdk. Any other software runs a method via API through POST /v1/start, with any HTTP client.
Next: what Pipelex is · documentation · your console · Discord
Prefer to run it yourself? The Pipelex runtime runs your methods on your own machine — it and the rest of our repositories are listed below.
A method is a reusable, typed AI procedure, written in MTHDS, an open standard, and saved as a .mthds file. Each step is explicit, each output is structured, and every run is repeatable.
domain = "articles"
main_pipe = "summarize_article"
[pipe.summarize_article]
type = "PipeLLM"
description = "Summarize an article for a given audience"
inputs = { article = "Text", audience = "Text" }
output = "Text"
prompt = "Summarize $article in three bullet points for $audience."From here, Pipelex handles model routing across providers, structured output parsing, and pipeline orchestration.
The Pipelex runtime runs methods on your own machine, against the model providers you choose or a local model; its README carries the install, the configuration and the first run. pipelex-api is the runner API you host yourself, and the editor extension highlights and checks .mthds files, from the VS Code Marketplace or the Open VSX Registry for Cursor, Windsurf and other VS Code forks.
Build and run your methods
| Repository | Description |
|---|---|
pipelex-plugins |
The Pipelex plugin for Claude Code and Codex: skills that build and run methods, a hook that checks every edit, and the Pipelex tools |
pipelex-mcp |
The Pipelex MCP, which ChatGPT or Claude adds to run the methods saved in your account |
pipelex-method-apps |
Template for turning a method into a webapp, with its input form and result view generated from the method |
pipelex-sdk-js |
TypeScript SDK for the Pipelex API (npm: @pipelex/sdk) |
pipelex-sdk-python |
Python SDK for the Pipelex API (PyPI: pipelex-sdk) |
pipelex-starter-js |
Starter template: a Next.js app that runs methods through @pipelex/sdk, with worked examples to copy |
pipelex-starter-python |
Starter template: a Python CLI that runs methods through pipelex-sdk |
n8n-nodes-pipelex |
n8n community node that runs methods on a Pipelex API server (npm: n8n-nodes-pipelex) |
Run it yourself
| Repository | Description |
|---|---|
pipelex |
The Pipelex runtime, which runs methods on your own machine (PyPI: pipelex) |
pipelex-api |
The runner API you host yourself, the reference implementation of the MTHDS Protocol (Docker Hub: pipelex/pipelex-api) |
vscode-pipelex |
The VS Code and Cursor extension, the plxt formatter and linter, and the language server for .mthds (PyPI: pipelex-tools) |
Methods and examples
| Repository | Description |
|---|---|
methods |
The public method library: packaged methods to run by their address or to fork |
pipelex-cookbook |
Examples and tutorials for the Pipelex runtime |
cocode |
Codebase analysis CLI built on Pipelex: changelogs, doc updates, drift proofreading (PyPI: cocode) |
The MTHDS standard
| Repository | Description |
|---|---|
mthds |
The MTHDS open standard: specification and docs (mthds.ai) |
mthds-js |
The mthds CLI and SDK for any MTHDS API (npm: mthds) |
mthds-python |
Python implementation of the MTHDS Protocol: a typed client and the base structures methods are defined in (PyPI: mthds) |
mthds-starter-js |
Starter template: a Next.js app running methods through the mthds SDK against any MTHDS API |
Libraries
| Repository | Description |
|---|---|
mthds-ui |
React graph viewer for method pipelines (npm: @pipelex/mthds-ui) |
mthds-form |
Headless form kernel and React controls for method inputs (npm: @pipelex/mthds-form) |
kajson |
JSON encoder and decoder for Python with pydantic v2 support, the serialization layer under pipelex (PyPI: kajson) |
- Discord: get help, share methods, meet the team
- Documentation: guides and reference
- GitHub Issues: report bugs and request features
- security@pipelex.com: security and privacy concerns
The runtime and the servers that run methods — pipelex, pipelex-api and pipelex-mcp — are source-available under the Elastic License 2.0 (ELv2). You may embed them in your own products, including services whose features run your methods, and run them for your own team or company; what the license rules out is hosting a service that runs methods for others. The license page explains how we read it, with concrete examples. Every version of them released before the switch stays under MIT.
The SDKs, the starter templates, the public method library, the cookbook, the UI libraries, the VS Code extension, the n8n node, cocode and the MTHDS open standard are MIT licensed. kajson and pipelex-plugins are licensed under Apache 2.0. Each repository's LICENSE file carries its terms.
"Pipelex" is a trademark of Evotis S.A.S.
