Skip to main content
Glama
pete-welch-db

Databricks Domo Migration Accelerator MCP Server

by pete-welch-db
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for the HTTP MCP server when using streamable HTTP. Default is '8000'.
GIT_TOKENNoGit token for linking GitHub or Azure DevOps to create PRs from generated bundles.
DOMO_INSTANCENoDomo instance domain (e.g., 'mycompany.domo.com') for live provider transform internals.
DOMO_CLIENT_SECRETNoDomo OAuth2 client secret for live provider. Must be set when domo_provider is 'live'.
DOMO_DEVELOPER_TOKENNoDomo developer token for instance API access when using live provider.
PSEUDO_DOMO_TRANSPORTNoTransport protocol for the MCP server. Set to 'http' to enable streamable HTTP. Default is 'stdio'.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
domo_discoverB

Inventory the Domo tenant for a migration assessment.

domo_inventoryB

Typed, searchable asset inventory of the Domo estate.

Domo work is organized by object type; this returns every asset with a common shape plus type-specific fields, optionally filtered.

domo_assessA

Assess the Domo estate: classify by data domain + source, score governance and migration complexity, and tag business value.

industry_model_mapA

Draft-map a Domo DataSet's columns onto a canonical industry-model table.

Conforms a Domo output DataSet to the Databricks Industry Data Model ("silver") so the transpiled pipeline lands governed, standard entities rather than a like-for-like copy.

list_industry_modelsB

List available Databricks Industry Data Models (and their domains).

lakeflow_feasibilityA

Score Domo source systems for Lakeflow Connect ingestion feasibility.

For each upstream source feeding the Domo estate, returns GREEN/AMBER/RED plus the recommended Databricks ingestion pattern (managed connector vs Auto Loader vs Lakebase re-platform) and a rationale — the input to sequencing the 28-source migration.

transpile_lineageA

Transpile one Domo lineage triplet into a Databricks SDP medallion.

Runs the 6-agent transpiler (Ingest -> Parse -> Emit -> BeastMode -> Repoint -> Reconcile) over a lineage's triplet (Magic ETL + DataSet schema

  • card Beast Modes) and returns the emitted bronze/silver/gold Spark SQL, the folded semantic-metrics view, the Domo->Databricks connector-swap plan, and the PASS/FAIL reconciliation gate.

migration_planA

Produce the prioritized Domo->Databricks migration plan.

Combines the tenant census, per-dataflow assessment, and per-source Lakeflow Connect feasibility into a wave-sequenced plan ranked by business value then migration complexity. This is the structured "assessment deliverable" a customer engagement produces.

Returns waves, the governance split, source feasibility rollup, and the recommended pilot. All figures are draft-grade until live tenant data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pete-welch-db/databricks-domo-migration-accelerator'

If you have feedback or need assistance with the MCP directory API, please join our Discord server