After a failed run
An analyst asks why the nightly revenue job did not finish. Memtro lists the recent runs, finds the failed one, quotes its error message and duration, and links to the run page in Databricks.
Unity Catalog tables, read-only SQL and job failures from Databricks, in plain English.
Connect a Databricks workspace with a personal access token and Memtro sees what you can see: SQL warehouses, Unity Catalog catalogs, schemas, tables and their columns, and the jobs that run there. It can run a single SELECT on a warehouse, cancelled after 30 seconds and capped at 500 rows, and list recent job runs with the error message for each failure. Nothing is written.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Databricks tool, reads what it needs, and answers with the source cited.
Once Databricks is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which jobs failed in the last 24 hours, and what did the error say?
What tables are in prod.sales, and what columns does prod.sales.orders have?
How many orders did we take per day last week, from prod.sales.orders?
Is the main SQL warehouse running, and who created it?
Show me the definition of the view analytics.finance.monthly_revenue
An analyst asks why the nightly revenue job did not finish. Memtro lists the recent runs, finds the failed one, quotes its error message and duration, and links to the run page in Databricks.
The head of sales wants last month's orders by region. Memtro reads the columns of prod.sales.orders, writes a SELECT with a date filter and a LIMIT, runs it on the warehouse and returns the rows.
The teams that lean on Databricks most, a question each of them asks, and what they connect beside it.
A record in Databricks is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Databricks open your profile (top right) → Settings → Developer → Access tokens → Generate new token; give it a lifetime, since the connection stops when it expires
Copy the workspace URL from the browser, without a path, and optionally the SQL warehouse ID from SQL Warehouses → the warehouse → Connection details (the last part of the HTTP path)
Paste them into Connections → Databricks in Memtro and connect; with no warehouse ID Memtro uses the first running warehouse you can see
Ask which jobs failed overnight, or what tables the sales schema holds
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Databricks tools are the same everywhere.
Not yet. Today every Databricks tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Workspace URL and personal access token. In Databricks open your profile (top right) → Settings → Developer → Access tokens → Generate new token; give it a lifetime, since the connection stops when it expires.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time