A quick count
The operations lead asks how many returns are waiting for inspection. Memtro counts rows in the Returns table where status is Received and answers 23, with the oldest from Brightwave Ltd logged on 28 October.
Ask how many rows in a NocoDB table match a condition, or read one record.
Connect NocoDB with an API token and Memtro reads your workspaces, bases, tables and fields, and rows filtered, sorted and counted with NocoDB's where syntax. The token acts as you, with your access to every workspace and base, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can add, change, upsert and link rows, comment, create bases, tables and fields, and run button actions or manual workflows, which may send messages or call outside services. Deleting rows, fields or tables is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right NocoDB tool, reads what it needs, and answers with the source cited.
These tools change something in NocoDB. 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 NocoDB 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 support requests in NocoDB are still open?
Which orders from Acme are marked unpaid?
What fields does the Inventory table have?
Mark the Northwind order as shipped
Add a Priority field to the Tickets table
The operations lead asks how many returns are waiting for inspection. Memtro counts rows in the Returns table where status is Received and answers 23, with the oldest from Brightwave Ltd logged on 28 October.
Sarah Collins asks Memtro to set the BigCo ticket row to Resolved and comment that the fix shipped. With the actions granted, Memtro changes only the status field of that row, replacing the old value, adds the comment for everyone with access to the base, and notes that NocoDB's API keeps no undo.
The teams that lean on NocoDB most, a question each of them asks, and what they connect beside it.
A record in NocoDB 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 NocoDB open Account settings → Tokens → Add new token, name it Memtro and copy it, shown once. It acts as you, so consider a dedicated user invited only to the right bases
Leave Host blank for NocoDB Cloud (app.nocodb.com), or type your self-hosted server's host name only, with a publicly trusted certificate. Releases without the v3 API are refused
Row comments need a Cloud Business plan or a licensed self-hosted NocoDB, and the rest works on every plan. Paste the API token into Connections → NocoDB in Memtro
Ask how many support requests are still open
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The NocoDB tools are the same everywhere.
Only when you ask, and only what it has been granted: add rows to a table; comment on a row; change fields of existing rows; delete rows from a table; add or update rows matched on up to three fields; create a table; rename a table or change its description or display field; delete a table and all its rows; add a field to a table; rename a field or change its description or default; delete a field and its data; link rows through a Link field; unlink rows on a Link field; edit a row comment; delete a row comment; resolve or reopen a row comment; run a button field's action on named rows; run a manual-trigger workflow; create a base in a workspace. 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 token. In NocoDB open Account settings → Tokens → Add new token, name it Memtro and copy it, shown once. It acts as you, so consider a dedicated user invited only to the right bases.
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