Other backend providers
Neon, Vercel Postgres, PlanetScale, and custom MCP backends are recognised by the connect API but not wired end-to-end in the product surface yet.
Status today
| Provider | Connect API | Workspace UI | Agent tools |
|---|---|---|---|
| Supabase Cloud | ✅ | ✅ | ✅ |
| Neon Postgres | ✅ (schema) | ❌ | Partial |
| Vercel Postgres | ✅ (schema) | ❌ | Partial |
| PlanetScale | ✅ (schema) | ❌ | Partial |
| Custom MCP endpoint | ✅ (schema) | ❌ | Partial |
Why Supabase first
Supabase ships database, auth, storage, and realtime under one anon key — a single connection unlocks the four things every web app needs. The other providers each cover one slice, so we are building a connector proxy that composes them into the same shape Supabase ships out of the box.
What the rollout looks like
- Neon Postgres — first to land after Supabase. Closest API shape; smallest delta in the agent tool layer.
- Vercel Postgres — same Postgres flavour as Neon under the hood; should ride the Neon work.
- PlanetScale — MySQL flavour, separate migration path. The RLS gate maps to row-based grants instead.
- Custom MCP — points the agent at a third-party MCP server. Auth is whatever your server enforces.
No ship date. Subscribe to the changelog or follow @mythos_new on X for updates.
Was this page helpful?