Ask whether a Supabase project is healthy, which migrations ran and what the advisors flag.
Connect Supabase with a personal access token and Memtro reads the management plane: projects, each service's health, edge functions, database branches, applied migrations and advisor findings. Project API keys, secrets, database passwords and the rows in your tables are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can pause, restore, restart or rename projects, create billable branches and apply SQL migrations to a live database. Merging a branch, applying a migration, and deleting a branch or edge function cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Supabase tool, reads what it needs, and answers with the source cited.
These tools change something in Supabase. 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 Supabase 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.
Is our Supabase production project healthy right now?
Has the add_invoices_table migration been applied to production?
Which tables does the security advisor say have RLS disabled?
Which members of the Acme organisation have MFA turned off?
Create a restore point on production, then restart the project
Support hears that sign-ups are failing and asks whether Supabase is up. Memtro checks the production project's services and reports that auth, rest and storage are healthy while the pooler shows an error, so the engineer on call starts there.
Priya Nair notices the old Northwind demo project is still running and asks Memtro to pause it. Memtro confirms nothing has deployed to it for months, then pauses it, which takes its database and API offline with the data kept until someone restores it.
The teams that lean on Supabase most, a question each of them asks, and what they connect beside it.
A record in Supabase 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.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn supabase.com/dashboard open Account → Access Tokens and generate a new token, scoped to the organisations and projects Memtro should see if you can
Give it read permissions, plus write on projects, environments (branches), database or edge functions only for what Memtro may change. A classic token carries all of your own access, so a scoped one is the better choice
Copy the token, which is shown once, then in Memtro open Connections → Supabase, paste the Personal access token and connect
Ask whether your production project is healthy
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Supabase tools are the same everywhere.
Only when you ask, and only what it has been granted: pause a project (its apps go offline); restore a paused project (resumes billed compute); restart a project's services (brief downtime); rename a project; create a database branch (billed hourly); merge a branch's migrations into its parent project; reset a branch to a migration version (branch data lost); delete a database branch (permanent); apply a SQL migration to a project's database; delete an edge function (permanent); create a named database restore point. 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.
Personal access token. In supabase.com/dashboard open Account → Access Tokens and generate a new token, scoped to the organisations and projects Memtro should see if you can.
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
