Which Xata branches are unhealthy or hibernated, and how busy is production?
Xata connects Memtro to your Postgres platform with branching. It reads organisations, projects and branches with their health, instances, region, size and scale-to-zero. It reads a branch's metrics over a window, such as CPU, memory, connections, latency and replication lag, plus backups with their restore window and your limits. When asked and granted, it can create, rename or delete a project, create, describe, hibernate, wake, resize or delete a branch, restore a backup into a new branch, and invite a member. Connection strings and credentials are never returned, and metric windows run to 30 days at most.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Xata tool, reads what it needs, and answers with the source cited.
These tools change something in Xata. 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 Xata 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 branches are not healthy right now?
What was the main branch's replication lag over the last day?
How far back can the production branch be restored?
What is our organisation's project limit?
Hibernate the preview branch.
Maya Okafor, backend engineer at BigCo, asked why the production branch felt slow that afternoon. Memtro read its metrics for the last few hours, giving CPU, active connections and read latency, beside the branch's instance type and replicas. She took the figures to her lead before deciding on a resize.
Dan Fletcher, platform lead at Acme Ltd, asked Memtro to restore the main branch to just before a faulty migration. With the action granted, Memtro restored the backup at that point into a new branch, leaving main unchanged. The new branch runs and bills until somebody deletes it.
The teams that lean on Xata most, a question each of them asks, and what they connect beside it.
A record in Xata 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
VectaraIn the Xata console, open Organization settings, then API keys, and create a key. Give it read-only access to Organization, Project, Branch and Metrics, and read and write only where Memtro should act.
In Memtro, open Connections → Xata and paste the API key. Fill in the organisation id only if the key sees more than one organisation.
An administrator grants the project, branch and invitation actions by name to the teams that may use them. Leave credentials at no access, as Memtro never reads them.
Ask which branches are not healthy.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Xata tools are the same everywhere.
Only when you ask, and only what it has been granted: create a project; rename a project; delete a project and all its branches; create a child branch from an existing branch; rename or describe a branch; hibernate or wake a branch; resize a branch (replicas, storage, instance type); delete a branch; restore a branch from backup into a new branch; invite someone to 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.
API key. In the Xata console, open Organization settings, then API keys, and create a key. Give it read-only access to Organization, Project, Branch and Metrics, and read and write only where Memtro should act.
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
