Authentication

Agent Explorer uses Clerk for user authentication. All features require a signed-in account.

The Explorer page after sign-in

Sign In Methods

Google OAuth — One-click sign in with your Google account
Email/Password — Sign in with email and password

Sign Up

New users can sign up at /sign-up. After creating an account you'll land on the Explorer page with two example resources auto-seeded — one mock A2A agent and one mock MCP server — so you have something to poke at immediately. You then have access to:

Personal Agents (real or mock)
Personal MCP Servers (real or mock)
Workspaces for grouping
Team membership (by invitation)

Sessions

Clerk manages session tokens automatically. Sessions are persisted across browser refreshes. Signing out clears all session data.

Route Protection

All routes except the docs, sign-in, and sign-up pages require authentication. Unauthenticated requests to API routes return 401 Unauthorized.

User Identity

Your Clerk userId is used to scope all personal resources (agents, MCP servers, workspaces, conversations). Team resources are shared by team membership.