
Databricks
Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение
Что умеет
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu
Список инструментов сервера (17)
Технические названия из tools/list. Нужны только разработчикам.
| databricks_list_accounts | Lista os workspaces Databricks conectados a este install — host, label. |
| databricks_current_user | Identifica o usuário do PAT no workspace (whoami via SCIM Me). Útil pra confirmar qual conta/host está conectado e validar o token. |
| databricks_list_warehouses | Lista os SQL warehouses do workspace (id, name, state, cluster_size, warehouse_type). Use o `id` em databricks_run_sql (ou deixe o run_sql escolher um RUNNING automaticamente). |
| databricks_get_warehouse | Detalha um ou mais SQL warehouses por id. Aceita lista (`ids`). |
| databricks_run_sql | Executa uma instrução SQL num SQL warehouse (Statement Execution API). Retorna colunas + linhas quando termina dentro do wait_timeout; senão devolve statement_id + state pra polling via databricks_get_statement. Se `warehouse_id` não for informado, escolhe um warehouse RUNNING automaticamente. PREFIRA queries parametrizadas (`parameters`) a interpolar valores na string (proteção contra SQL injection). SQL é arbitrário (pode DML/DDL) — confirme antes de mutar dados. Bulk support: accepts warehouse_ids for batched execution. |
| databricks_get_statement | Status + resultado de um ou mais statements por id (polling de queries longas que voltaram PENDING/RUNNING do run_sql). Aceita lista (`statement_ids`). |
| databricks_cancel_statement | Cancela um ou mais statements em execução por id. Aceita lista (`statement_ids`). |
| databricks_list_catalogs | Lista os catálogos do Unity Catalog visíveis ao PAT (name, comment, owner). |
| databricks_list_schemas | Lista os schemas (databases) de um catálogo Unity. Informe `catalog_name`. |
| databricks_list_tables | Lista as tabelas de um schema Unity (name, table_type, data_source_format). Informe `catalog_name` e `schema_name`. |
| databricks_get_table | Detalha uma ou mais tabelas (colunas, tipos) por nome completo `catalog.schema.table`. Aceita lista (`full_names`). |
| show_version | Show the current MCP platform and adapter versions. |
| report_bug | Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. |
| connect | Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs. |
| toolkit_info | Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes. |
| marketplace | The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login. |
| authenticate | MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link. |