Nextbase Docs
Nextbase Docs
HomeBlogWelcome to Nextbase v5!Choose your starterGetting startedLocal Supabase per agent
AuthenticationWorkspaces and the admin area
User and admin MCPsConnect an agentTools and permissions
Building with agentsEmails with Resend
TroubleshootingNextbase v5
Using your app with agents

Connect an agent

Copy your server address, sign in and approve access to one workspace.

You need an agent client that supports remote Streamable HTTP MCP, OAuth and public dynamic client registration. The exact labels in its settings will depend on the client.

1. Open your connection settings

Sign in to the app and open Agent connections. Use these paths if you want to go there directly:

KitsUser connectionsAdmin connections
Supabase, Neon and D1/mcp/connections/user on the web app/mcp/connections/admin on the admin app
Convex/user/settings/connections on the web app/app-admin/connections on the admin app

The admin page requires an application administrator account. Every kit ships a separate admin app with its own origin (the demos use a -admin subdomain), and that is where the admin connections page lives. See your kit's agent connections page for the exact addresses.

2. Copy the server address

Copy the URL shown on that page into your agent's remote MCP settings. Select OAuth authentication.

For the live demos, the user servers are:

StarterUser MCP
Next.js Supabasehttps://nextjs-supabase.usenextbase.com/mcp/user
TanStack Supabasehttps://tanstack-supabase.usenextbase.com/mcp/user
Next.js Convexhttps://dynamic-grasshopper-80.convex.site/mcp/user
TanStack Convexhttps://ceaseless-lark-846.convex.site/mcp/user
Next.js Neonhttps://nextjs-neon.usenextbase.com/mcp/user
TanStack Neonhttps://tanstack-neon.usenextbase.com/mcp/user
Next.js D1https://nextjs-d1.usenextbase.com/mcp/user
TanStack D1https://tanstack-d1.usenextbase.com/mcp/user

For the admin server, replace the final /user with /admin. Use your own app's addresses when you deploy your product; the table above points to the demos.

3. Review the connection

The agent opens the consent page. Sign in with your normal account if needed. Check the callback address and permissions, then select the workspace you want the agent to use.

Client names are supplied by the client itself. The consent screen marks them as unverified, so use the callback address and the client you started from to check the request.

Supabase, Neon and D1 offer read access. Convex offers an additional project creation permission when it is requested and you choose to allow it.

4. Try a tool

Ask the agent to list projects in the selected workspace. If you are testing an admin connection, ask it to list workspaces.

A blank project list can be valid. Add a project through the website and try again.

5. Disconnect when you are done

Open the connection settings and use Disconnect or Revoke, depending on the kit. Signing out of the session that approved the connection also ends its access.

Access tokens are short-lived. Connections can refresh for up to 30 days, but may end sooner with the original sign-in session. If access has ended, start a new connection.

If the client never opens consent or loops through login, see troubleshooting.

User and admin MCPs

Let an agent use your app through a connection the user can approve and revoke.

Tools and permissions

What each connection can do in the v5 release.

On this page

1. Open your connection settings2. Copy the server address3. Review the connection4. Try a tool5. Disconnect when you are done