Nextbase v5
The eight starter kits and the agent connections included in this release.
Released on 14 October 2026.
v5 brings all 8 starter kits into one documented lineup. Each kit has a user MCP and an admin MCP, while keeping its existing authentication provider.
The kits
- Next.js + Supabase
- TanStack + Supabase
- Next.js + Convex
- TanStack + Convex
- Next.js + Neon
- TanStack + Neon
- Next.js + Cloudflare D1
- TanStack + Cloudflare D1
Each has its own docs section with installation, environment variables, authentication, agent connections, project structure and deployment pages, plus a live demo. The two repositories with PlanetScale in their names now use Neon Postgres.
Agent connections
Users can connect an agent to one workspace. Administrators use a separate server to look up users and workspaces across the application.
OAuth handles sign in, consent and credentials for the connection. The website has settings to inspect and revoke access. The original auth provider, account and workspace rules are preserved.
All kits support reading account context and projects through the User MCP. Both Convex kits additionally support project creation with explicit write consent. The remaining six User MCPs and all eight Admin MCPs are read-only.
What was checked?
The release checks covered native authentication, consent, user/admin separation, permissions, token refresh and revocation. Full authorized MCP flows were exercised against isolated real backends with the official MCP SDK. The published sites were also checked for discovery, auth challenges and their connection/login routes.
For Supabase, Neon and D1, production test accounts also completed sign in, connection settings, workspace consent and cancellation. These checks did not create delegated production access grants.
If you are comming from v4
Choose the v5 repository that matches your stack first. Treat moving an existing app as a migration: review its auth, data model and integrations before moving production data.
Things to keep in mind
Provider credentials are still needed for optional billing, storage, analytics, email and social login integrations in your own deployment. These docs describe what is included and how to configure it; they don't turn on every external service for you.
The Next.js Convex kit's main auth, onboarding, workspace and project paths use Convex. Some older advanced application pages still have Supabase-based actions and need migration before you rely on those paths. The kit page calls this out too.
We'll keep adding to the docs as the kits grow. If something is missing, start with the repository README and the setup steps for the kit you picked.