Numbers for the board
The founder asks how many orders shipped last month and their total value. Memtro reads the schema, runs one limited query over the orders table under the Memtro role, and returns 1,284 orders worth £96,400.
Ask Hasura questions about your own tables, answered with a GraphQL query.
Connect Hasura v2 with your host name and admin secret and Memtro reads the schema and runs GraphQL queries over your own tables. Hasura is self-hostable, and Memtro talks to your server or your Hasura Cloud v2 project. The admin secret cannot be scoped, so set a role and every request runs under that role's rules. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can run insert, update and delete mutations, which change or permanently delete rows and cannot be undone from Memtro.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Hasura tool, reads what it needs, and answers with the source cited.
These tools change something in Hasura. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Hasura, choosing the same kinds; the tab shows Hasura's own steps. Each event can start a job, with the event as its input. Hasura sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Hasura 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.
How many orders are still open, and what is their total?
Which customers signed up in the last 30 days?
What tables can Memtro query?
Mark order 5521 as cancelled
Which Northwind invoices are more than 60 days overdue?
The founder asks how many orders shipped last month and their total value. Memtro reads the schema, runs one limited query over the orders table under the Memtro role, and returns 1,284 orders worth £96,400.
Support asks Memtro to correct the email on the Brightwave Ltd customer record. Memtro runs one update mutation on that row by its key, and the role's update permissions decide whether it is allowed.
The teams that lean on Hasura most, a question each of them asks, and what they connect beside it.
A record in Hasura 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.
Needs Hasura v2 (Community, Enterprise or Hasura Cloud v2); Hasura DDN (v3) is not supported
Create a Hasura role for Memtro with select permissions on what it may read, and insert, update or delete only where it may write
In Connections → Hasura in Memtro type your host name only, with no https:// or /v1/graphql, paste the admin secret and set the role
Ask how many orders are still open
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Hasura tools are the same everywhere.
Only when you ask, and only what it has been granted: run an insert mutation in Hasura (an upsert only when asked); run an update mutation in Hasura; run a delete mutation in Hasura. 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.
Host and admin secret. Needs Hasura v2 (Community, Enterprise or Hasura Cloud v2); Hasura DDN (v3) is not supported.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Hasura, choosing the same kinds; the tab shows Hasura's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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