PipelineFlow
# PipelineFlow MCP (Lite Edition)
[](LICENSE)
[](https://modelcontextprotocol.io/)
[](https://python.org/)
**PipelineFlow MCP** is a lightweight, declarative workflow DAG and data pipeline orchestrator designed for AI agents (Claude Desktop, Cursor, OpenAI Codex, LangGraph).
It enables agents to define multi-step data pipelines, validate dependency acyclicity via topological sorting (Kahn's algorithm), execute transformations predictably, and export visual Mermaid diagramsβwithout heavy cloud orchestrators like Airflow or Prefect.
---
## π― The Problem
When autonomous AI agents execute multi-step workflows:
1. **Unstructured Command Chains:** Agents run disconnected shell commands or Python scripts with no dependency graph or cycle detection.
2. **Lack of Visual Representation:** Neither humans nor agents can visualize the pipeline topology or inspect intermediate step outputs.
3. **Heavy Orchestrator Bloat:** Enterprise orchestrators (Airflow, Dagster) require databases, workers, and gigabytes of dependencies, making them unsuitable for local agent runtimes.
**PipelineFlow** provides a pure-Python, zero-dependency DAG engine that runs directly inside the MCP protocol.
---
## β¨ Features (Lite Edition)
- π **Declarative Pipeline DAG:** Add nodes (inputs, filters, transforms, aggregates, outputs) and connect directed edges.
- π‘οΈ **Cycle Detection & Topological Sort:** Guarantees deterministic execution order and prevents circular deadlocks using Kahn's algorithm.
- π **Instant Mermaid Diagrams:** Generates clean Mermaid graph diagrams of any pipeline with one tool call.
- β‘ **Zero-Dependency Engine:** Pure standard library execution with zero cloud setup.
---
## π Quickstart
### 1. Installation
```bash
git clone https://github.com/johannschiffer/pipelineflow-mcp.git
cd pipelineflow-mcp
pip install -e .
```
### 2. Configure in Claude Desktop or Cursor
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"pipelineflow": {
"command": "pipelineflow",
"args": ["run"]
}
}
}
```
### 3. Run Demo via CLI
```bash
pipelineflow demo
```
---
## π οΈ MCP Tools Reference
| Tool | Parameters | Description |
|---|---|---|
| `create_pipeline` | `pipeline_id`, `name` | Creates a new pipeline DAG |
| `add_node` | `pipeline_id`, `node_id`, `node_type`, `params` | Adds a node (input, filter, transform, aggregate, custom, output) |
| `connect_nodes` | `pipeline_id`, `from_node`, `to_node` | Connects source node to target node (validates acyclicity) |
| `run_pipeline` | `pipeline_id`, `initial_data` | Executes pipeline in topological dependency order |
| `get_node_output` | `pipeline_id`, `node_id` | Retrieves execution output for any node |
| `export_pipeline_mermaid` | `pipeline_id` | Returns Mermaid diagram string of the pipeline graph |
| `list_pipelines` | *(none)* | Lists all registered pipelines and node counts |
---
## π Upgrade to PipelineFlow Pro
Need enterprise pipeline caching, parallel branch execution, and interactive HTML dashboards?
The **PipelineFlow Pro Edition** adds:
- β‘ **Content-Addressable Cache (SQLite WAL):** Caches node execution outputs by SHA-256 hash of inputs, skipping redundant executions.
- π **Concurrent Branch Runner:** Runs independent DAG branches in parallel using a managed thread pool.
- π‘οΈ **Per-Node Retry & Circuit-Breaker Policies:** Configurable exponential backoff and error recovery.
- π¨ **Interactive HTML Visualizer:** Generates standalone interactive SVG/HTML pipeline dashboards.
- π³ **Production Docker & Docker Compose manifests.**
- π§ͺ **100% Passing Pytest Suite.**
π **[Get PipelineFlow Pro on Gumroad ($14.99 USD)](https://johanld.gumroad.com/l/ykees)**
---
## π License
MIT Β© 2026 [Johann Schiffer](https://github.com/johannschiffer)
TDQS
Scored across 7 tools
Each tool targets a distinct pipeline-building action: create_pipeline, add_node, connect_nodes, run_pipeline, get_node_output, export, and list are largely separable. The only mild overlap is between run_pipeline (executes and collects outputs) and get_node_output (fetches cached output), but the descriptions clarify execution vs. retrieval.
All seven tools use a consistent snake_case verb_noun pattern (create_pipeline, add_node, connect_nodes, run_pipeline, get_node_output, list_pipelines). export_pipeline_mermaid is slightly longer but still follows the same verb_noun convention.
Seven tools is well-scoped for a pipeline DAG builder/runner, covering construction, execution, inspection, and export without redundancy. Every tool earns its place.
The surface covers creation, node/edge building, execution, output retrieval, listing, and export, but has notable gaps: no delete_pipeline, no update/rename, and no remove_node or disconnect_nodes, so agents cannot clean up or modify an existing DAG. These missing lifecycle operations will force workarounds.