Which Upstash databases are closest to their limits, and what did they cost this month?
Upstash connects Memtro to your serverless Redis and Vector account. It reads Redis databases with plan, state, regions, limits, eviction, TLS and backups, and one database's usage, from latency to monthly requests, storage, bandwidth and cost. It reads backups, vector indexes, teams and the audit log. When asked and granted, it can create, rename or delete a database, set its budget, change eviction, auto upgrade, TLS and daily backups, create, delete or restore backups, rename or delete a vector index, and manage team members. Credentials are never returned, and 30-day stats need a Pro plan or the Production Pack.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Upstash tool, reads what it needs, and answers with the source cited.
These tools change something in Upstash. 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 Upstash 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 are closest to their storage limits?
What did the sessions database cost this month?
Did the latest backups of the orders database complete?
Which vector indexes use cosine similarity?
Turn on daily backups for the sessions database.
Tom Reilly, backend lead at BigCo, asked what the sessions database had cost this month and why. Memtro read its usage, giving this month's requests, storage, bandwidth and cost beside its peak throughput. He set a lower monthly budget the same day.
Priya Sharma, platform engineer at Acme Ltd, asked Memtro to back up the orders database before a schema change. With the action granted to her team, Memtro took a named backup, then listed the database's backups to show it had completed. Her team could see it in the Upstash console.
The teams that lean on Upstash most, a question each of them asks, and what they connect beside it.
A record in Upstash 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 Upstash console, open Account, then Developer API, and choose Create API Key. Pick Read Only for reads or Read/Write for actions, and copy the key, as it is shown once.
In Memtro, open Connections → Upstash and paste the Account email you sign in with and the Developer API key.
An administrator grants the database, backup and team actions by name to the teams that may use them, and only a Read/Write key can carry them out.
Ask which databases are closest to their limits.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Upstash tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Redis database (pay as you go bills by use); rename a Redis database; delete a Redis database; set a database's monthly budget; turn eviction on or off; turn off auto upgrade; enable TLS on a database; create a backup; delete a backup; restore a backup over a database; turn daily backups on or off; rename a vector index; delete a vector index; add a member to a team; remove a member from a team. 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.
Account email and developer API key. In the Upstash console, open Account, then Developer API, and choose Create API Key. Pick Read Only for reads or Read/Write for actions, and copy the key, as it is shown 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
