Other · Local MCP server
Mlflow
MLflow MCP - experiments, runs, registered models, versions, traces, assessments (MLflow 3)
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.us-all/mlflow- Version
- 1.12.7
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-19
- Updated
- 2026-06-19
- Publisher
- us-all (GitHub) · 8 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/us-all) · how
- Repository
- github.com/us-all/mlflow-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @us-all/mlflow-mcp | 1.12.7 | stdio |
How to connect Mlflow
Mlflow runs locally from a Node.js package published to the npm registry: @us-all/mlflow-mcp version 1.12.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @us-all/mlflow-mcp@1.12.7. It reads these environment variables: MLFLOW_TRACKING_URI (required), MLFLOW_TRACKING_TOKEN (secret), MLFLOW_TRACKING_USERNAME, MLFLOW_TRACKING_PASSWORD (secret), MLFLOW_EXPERIMENT_ID, MLFLOW_TOOLS, MLFLOW_DISABLE and MLFLOW_ALLOW_WRITE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mlflow": {
"command": "npx",
"args": [
"-y",
"@us-all/mlflow-mcp@1.12.7"
],
"env": {
"MLFLOW_TRACKING_URI": "<value>",
"MLFLOW_TRACKING_TOKEN": "<secret>",
"MLFLOW_TRACKING_USERNAME": "<value>",
"MLFLOW_TRACKING_PASSWORD": "<secret>",
"MLFLOW_EXPERIMENT_ID": "<value>",
"MLFLOW_TOOLS": "<value>",
"MLFLOW_DISABLE": "<value>",
"MLFLOW_ALLOW_WRITE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from us-all (GitHub)
| Server | Runs |
|---|---|
| AirflowAirflow MCP - list DAGs/runs/task instances, tail logs, trigger and clear (write-gated) | Local · stdio |
| AndroidAndroid MCP - ADB-based device, apps, UI, logcat, emulator, files, system, debug. | Local · stdio |
| DatadogDatadog MCP - 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet. | Local · stdio |
| DbtDbt MCP - manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres) | Local · stdio |
| Google DriveGoogle Drive + Workspace MCP - Docs, Sheets, Slides, Shared Drives, Labels, Approvals, DWD. | Local · stdio |
| OpenmetadataOpenMetadata MCP - metadata, lineage, search, data quality, OM 1.12+ Data Contracts. | Local · stdio |
| UnifiUniFi semantic-analysis MCP - fleet health, anomaly detection, cross-site analytics. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| MixpanelQuery Mixpanel events, funnels, retention, segmentation and insights (JQL). | Remote · HTTPLive check: ✓ handshake |
| Mixpanel MCPQuery Mixpanel events, funnels, retention, cohorts, and user profiles. | Local · stdio |
| Mixx Dj MCPFastMCP server for Mixxx DJ software control via OSC protocol. | Local · stdio |
| Mlb MCPTeams, schedules, and standings from the official MLB Stats API. No key required. | Local · stdio |
| Mlua SwarmMCP server for mlua-swarm: engine that compiles flow.ir Blueprints and dispatches agent steps. | Local · stdio |
| MMW Managed Memory WorkspaceUltra-fast persistent memory workspace with tenant isolation and cross-model continuity. | Remote · HTTPLive check: sign-in required |
| MnemaLocal-first, formally verified memory for AI agents: consult/learn/related/list over MCP. | Local · stdio |
| Mneme Decision MCPLocal MCP server for architectural decisions, traceability, and non-authoritative proposals. | Local · stdio |