Orders by status
Priya Sharma, a commercial analyst at Northwind, asked for last month's order count by status. Memtro looked up the member names in the Cube model, ran the query against the semantic layer, and gave her the count for each status.
What was our order count by status last month, straight from the Cube model?
Cube Cloud is the semantic layer over your warehouse. Memtro reads deployments, the data model's measures and dimensions, and answers questions by querying it. It also reads workbooks, reports and their deliveries, AI scheduled tasks, dashboard notification schedules and build status. When asked and granted, it can create, change, run and delete scheduled tasks, schedule dashboard notifications and manage recipients, create, copy, publish and delete workbooks, refresh and delete reports, and run deliveries. Each query runs SQL on your warehouse and may cost compute, and notification schedules need an admin's key.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cube Cloud tool, reads what it needs, and answers with the source cited.
These tools change something in Cube Cloud. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Cube Cloud 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.
What was our order count by status last month in Cube?
Which measures does the orders cube have?
Did the latest build of the production model succeed?
Which AI scheduled tasks run every morning, and who do they notify?
Refresh the weekly revenue report.
Priya Sharma, a commercial analyst at Northwind, asked for last month's order count by status. Memtro looked up the member names in the Cube model, ran the query against the semantic layer, and gave her the count for each status.
Dan Fletcher, a finance lead at BigCo, asked Memtro to send the revenue dashboard as a PDF every Monday to Maya Okafor. Memtro scheduled the notification and added Maya, so each Monday's render is emailed to her.
The teams that lean on Cube Cloud most, a question each of them asks, and what they connect beside it.
A record in Cube Cloud 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 Cube Cloud, open Admin → API Keys and create a key scoped to the deployments Memtro should see. Only admins hold keys unless all users may create them.
In Memtro, open Connections → Cube Cloud and paste the API key and the Cube Cloud host you sign in at, without https://.
If you limit the key to specific endpoints, include the deployment token endpoint. An administrator grants the task, notification and workbook actions by name to the teams that may use them.
Ask what your order count by status was last month in Cube.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cube Cloud tools are the same everywhere.
Only when you ask, and only what it has been granted: create an AI scheduled task; change, pause or resume a scheduled task; delete a scheduled task; run a scheduled task now; schedule a dashboard notification; add recipients to a dashboard notification; remove recipients from a dashboard notification; delete a dashboard notification; create a workbook; copy a workbook; delete a workbook; publish a workbook's dashboard draft; refresh a report; delete a report; run a report delivery to its spreadsheet now. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
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.
API key and Cube Cloud host. In Cube Cloud, open Admin → API Keys and create a key scoped to the deployments Memtro should see. Only admins hold keys unless all users may create them.
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