Generate Databricks App MCP servers from OpenAPI specs
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"uc-mcp-gen","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# uc-mcp-gen A CLI that compiles an OpenAPI spec directly into a self-contained [Databricks App](https://docs.databricks.com/en/dev-tools/databricks-apps/index.html) bundle — a runnable MCP server with one concrete Python function per API operation. Auth and routing are handled by a [Databricks Unity Catalog connection](https://docs.databricks.com/en/connect/unity-catalog/index.html). ## How It Works 1. Point `uc-mcp-gen generate` at an OpenAPI spec (local file or URL, YAML or JSON) 2. Provide a UC connection name 3. Get a self-contained Databricks App bundle back — ready to deploy with `databricks bundle deploy` The generated `main.py` has zero dependency on `uc_mcp_gen`. It's a plain FastMCP server where every API operation becomes a typed `async def` tool function, with all HTTP calls proxied through your UC connection. ## Install ```bash # Run without installing (recommended) uvx uc-mcp-gen generate ... # Or install locally for development uv sync ``` ## Usage ```bash uc-mcp-gen generate <spec> --connection <conn-name> [--name <service-name>] [-o <output-dir>] ``` **Arguments:** | Argument | Description | |---|---| | `spec` | Path or URL to OpenAPI spec (`.yaml`, `.yml`, `.json`, or remote URL) | | `--connection` | UC connection name in your Databricks workspace | | `--name` | Service name (kebab-case). Derived from spec title if omitted. | | `-o / --output` | Output directory. Defaults to `generated_mcp_servers/<name>-app`. | **Examples:** ```bash # From a local YAML spec uc-mcp-gen generate openapi.yaml --connection my-slack-conn -o ./slack-app # From a local JSON spec uc-mcp-gen generate openapi.json --connection my-api-conn # From a remote spec uc-mcp-gen generate https://api.example.com/openapi.yaml --connection my-conn -o ./example-app ``` ## Generated Bundle ``` <output>/ ├── databricks.yml Databricks Asset Bundle manifest ├── app.yaml App startup config — sets UC_CONNECTION_NAME ├── pyproject.toml App…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.