Which Turso databases read the most rows this month, and how close are we to plan limits?
Turso connects Memtro to your hosted SQLite organisation. It reads your databases with group, primary region, protection and any blocked reads or writes, and one database's configuration, instances and replicas. It reads a database's usage and top queries, groups and their locations, the organisation's plan, usage and limits, members and roles, and the audit log. When asked and granted, it can create, configure or delete a database, manage groups and their locations, and invite, re-role or remove members. It never reads table data, and the audit log needs the Scaler plan or above.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Turso tool, reads what it needs, and answers with the source cited.
These tools change something in Turso. 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 Turso 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 databases read the most rows this month?
How close is the organisation to its plan's database and storage limits?
Which locations does the production group replicate to?
Who are the admins in our Turso organisation?
Turn on delete protection for the production group.
Sarah Chen, backend lead at Acme Ltd, asked why the orders database was doing so much work this month. Memtro read its usage, with rows read and written per instance, and its top queries by rows read. She added an index for the query at the top of the list that afternoon.
Dan Fletcher, platform engineer at Northwind, asked Memtro to turn on delete protection for the production group. With the action granted to his team, Memtro switched it on, so neither the group nor its databases can now be deleted. A later delete request was refused until protection came off.
The teams that lean on Turso most, a question each of them asks, and what they connect beside it.
A record in Turso 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.
Grist
NocoDB
Typesense
Weaviate
Tinybird
Hightouch
Census
kintone
Monte Carlo
OpenMetadata
Secoda
Softr
Teable
VectaraWith the Turso CLI, run turso org list to find your organisation's slug, then run turso auth api-tokens mint memtro with --org and that slug. Copy the token, as the CLI prints it once.
In Memtro, open Connections → Turso and paste the Organization slug and the Platform API token.
For reads only, mint the token with --scope read --scope org:read, though a scoped token cannot manage members. An administrator grants the database, group and member actions by name to the teams that may use them.
Ask which databases read the most rows this month.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Turso tools are the same everywhere.
Only when you ask, and only what it has been granted: create a database in a group, optionally copied from another database (counts toward plan limits); change a database's size limit, delete protection, or block its reads or writes; delete a database; create a group in a location (counts toward plan limits); delete a group and every database in it; turn a group's delete protection on or off; unarchive a group archived for inactivity; upgrade every database in a group to the latest libSQL version; add a location (replica) to a group; remove a location from a group; invite a person to the organization by email or username; cancel a pending invite; change a member's role; remove a member from the organization. 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.
Organization slug and platform API token. With the Turso CLI, run turso org list to find your organisation's slug, then run turso auth api-tokens mint memtro with --org and that slug. Copy the token, as the CLI prints it once.
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
