Board prep
The CEO asks for the numbers behind the Revenue dashboard. Memtro lists its cards, runs the MRR and churn questions and returns both tables with the SQL each one executes.
Run your saved questions and ad-hoc SQL through Metabase
Connect Metabase with an API key and Memtro can find and run saved questions, read dashboards, browse the tables Metabase knows about and run read-only SQL, all under the permissions of the group you choose for the key.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Metabase tool, reads what it needs, and answers with the source cited.
The CEO asks for the numbers behind the Revenue dashboard. Memtro lists its cards, runs the MRR and churn questions and returns both tables with the SQL each one executes.
Marketing wants signups by campaign for last week. Memtro looks up the events table in the metadata, writes a SELECT with a GROUP BY and runs it through Metabase, so the key's group permissions still apply.
Questions people ask once Metabase is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from Metabase in Memtro, with the rest of their stack attached.
A record in Metabase is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, 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.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Metabase tools are the same everywhere.
Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.