
agentl
io.github.arimayujiPublished by GitHub account arimayujiv0.9.0Updated Oct 30, 2026
Validate, plan, preview and run YAML data pipelines (ETL with LLM steps) and debug failed runs.
Overview
Local MCP server that lets an assistant validate, plan, preview and run YAML data pipelines with LLM steps, and debug failed runs.
- What you can do
- Validate and plan YAML-defined ETL pipelines before executing them.
- Preview pipeline output and run pipelines end to end, including steps that call an LLM.
- Inspect and debug runs that failed, using a run store kept in SQLite or PostgreSQL.
- Create new pipelines with a configured model and provider.
- When to use it
- Useful when you build or maintain YAML-based ETL pipelines that mix data transforms with LLM steps, and want an assistant to check definitions, dry-run them, execute them, and investigate failures without leaving the chat.
- Requirements
- Runs locally over stdio, launched with uvx from the agentl-etl PyPI package, so a Python/uv environment is needed. A run store is configured via AGENTL_DB (SQLite path or postgresql:// URL, default .agentl/agentl.db). Creating pipelines needs AGENTL_MODEL and AGENTL_PROVIDER, plus whatever credentials the chosen LLM provider requires. Desktop only.
Installation
In SourceWeft
- Open agentl 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
This repository has no README.
Tools
0Version history
1- v0.9.0LatestOct 16, 2026
Score
25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.