Metaflow MCP Server
Give your coding agent superpowers over your Metaflow workflows. Instead of writing throwaway scripts to check run status or dig through logs, just ask -- your agent will figure out the rest.
Works with any Metaflow backend: local, S3, Azure, GCS, or Netflix internal.
Tools
| Tool | Description |
|---|---|
get_config |
What backend am I connected to? (also returns your default namespace) |
list_flows |
What flows exist in a namespace? |
search_runs |
Find recent runs of any flow |
get_run |
Step-by-step breakdown of a run |
get_task_logs |
Pull stdout/stderr from a task |
list_artifacts |
What did this step produce? |
get_artifact |
Grab an artifact's value |
get_latest_failure |
What broke and why? |
search_artifacts |
Which runs produced a named artifact? |
Quickstart
pip install metaflow-mcp-server
claude mcp add --scope user metaflow -- metaflow-mcp-server
That's it. Restart Claude Code and start asking questions about your flows.
To upgrade:
pip install --upgrade metaflow-mcp-server
Then restart Claude Code (or reconnect via /mcp) to pick up the new version.
If Metaflow lives in a specific venv, point to it:
claude mcp add --scope user metaflow -- /path/to/venv/bin/metaflow-mcp-server
For other MCP clients, the server speaks stdio: metaflow-mcp-server
How it works
Wraps the Metaflow client API. Whatever backend your Metaflow is pointed at, the server uses too -- no separate config needed. Sets namespace(None) at startup so production runs (Argo, Step Functions, Maestro) are visible alongside your dev runs.
Starts once per session, communicates over stdin/stdout. No daemon, no port.
License
Apache-2.0
1 maintainer
Metadata
1 maintainer
Release files for metaflow-mcp-server 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| metaflow_mcp_server-0.5.0.tar.gz | 34.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metaflow_mcp_server-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.5 kB
Release files / metaflow_mcp_server-0.5.0.tar.gz
| Download URL | metaflow_mcp_server-0.5.0.tar.gz |
|---|---|
| Size | 34.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e21a8ea55091a8813c5206781c13f805e9ecc2918be8b93f1fa9757bffcbce12
|
|
BLAKE2b-256 checksum How to use checksums |
a63e6c40151ee96307749078875639717aada11245c5e8a2967b9db9cc0524a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logRelease files / metaflow_mcp_server-0.5.0-py3-none-any.whl
| Download URL | metaflow_mcp_server-0.5.0-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
483aebeac96270c745848643290549a7fc40a277c69e8cef796b92f862abf914
|
|
BLAKE2b-256 checksum How to use checksums |
8333b24368b8c5cc12099e5332df7d698bb96fe66032169a1f1026768f0a02fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logSecurity for metaflow-mcp-server 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for metaflow_mcp_server-0.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
