Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
MLflow on Databricks (BYOK) icon

MLflow on Databricks (BYOK)

Read the MLflow experiments, runs, metric history, artifacts and model registry of your AWS Databricks workspace with your own personal access token

Unify Dynamics LLC

Tools11read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderMLflow on Databricksunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which MLflow experiments does my Databricks workspace have?
Tools called
search_experiments
What is MLflow experiment 1234567890 in my workspace?
Tools called
get_experiment
Find the MLflow experiment called /Shared/churn-model
Tools called
get_experiment_by_name
Which runs in experiment 1234567890 have rmse below 1?
Tools called
search_runs
What were the metrics and parameters of MLflow run abc?
Tools called
get_run
Show the loss curve of MLflow run abc
Tools called
get_metric_history

About

MLflow on Databricks (BYOK) lets an AI assistant read your own MLflow on Databricks data through the MLflow on Databricks API with a key you supply (Databricks personal access token). Read-only: 11 tools (search_experiments, get_experiment, get_experiment_by_name, search_runs, get_run, get_metric_history, list_run_artifacts, search_registered_models, get_registered_model, search_model_versions, get_model_version). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.cloud.databricks.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by MLflow on Databricks. MLflow on Databricks and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the MLflow on Databricks API (*.cloud.databricks.com) with a BYOK key; documentation: https://docs.databricks.com/api/workspace/experiments. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

11 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data11 tools
  • Search experimentsSearch MLflow experiments of the workspace by name or tag filter, with lifecycle stage, location and update time (Unix milliseconds).
  • Get experimentGet one MLflow experiment by id: name, artifact location, lifecycle stage, tags and times.
  • Get experiment by nameFind one MLflow experiment by its exact name (on Databricks this is the workspace path such as /Users/me@example.com/churn).
  • Search runsSearch the runs of one experiment, optionally with a filter on metrics, params or tags, newest first, with their metrics and params.
  • Get runGet one MLflow run: status, start and end time (Unix milliseconds), latest metrics, params and tags.
  • Get metric historyList all logged values of one metric of a run with step and timestamp, for example a training loss curve.
  • List run artifactsList the artifact files and folders of a run (one directory level) with path, size and whether it is a directory.
  • Search registered modelsSearch the workspace model registry (legacy, non Unity Catalog) by name, with latest versions and update time.
  • Get registered modelGet one registered model of the workspace registry: description, tags, latest versions and times.
  • Search model versionsSearch model versions of the workspace registry with a filter such as name='churn-model', with stage, status and source run.
  • Get model versionGet one version of a registered model: stage, status, source run, description, tags and times.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-mlflow-databricks.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Recurly Finance Config (BYOK)

Read your Recurly general ledger accounts, performance obligations, business entities, dunning campaigns, invoice templates, custom fields and export dates with your own private API key

Live · MCP + REST8 tools

Recurly Catalog (BYOK)

Read your Recurly plan details, plan add-ons, items, coupons, measured units, shipping methods and price segments with your own private API key

Live · MCP + REST9 tools

Flutterwave Config (BYOK)

Read Flutterwave supported banks and branches, fee quotes, payment plans, bill categories, settlements and chargebacks with your own v3 secret key

Live · MCP + REST12 tools

PostHog Audiences and Actions (BYOK)

Read your PostHog cohorts, actions and annotations, and where each cohort is used, with your own personal API key

Live · MCP + REST7 tools

PostHog Surveys (BYOK)

Read your PostHog surveys, their questions, schedule and response statistics with your own personal API key

Live · MCP + REST5 tools

PostHog Experiments (BYOK)

Read your PostHog A/B experiments, their status and health findings, and their activity history with your own personal API key

Live · MCP + REST5 tools

Get MLflow on Databricks (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own MLflow on Databricks Databricks personal access token. Create one at https://docs.databricks.com/aws/en/dev-tools/auth/pat, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to MLflow on Databricks. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with MLflow on Databricks.