Skip to main content
Soria uses Clerk-backed authentication. You sign in through a browser login page, and the same identity is used across the web UI and MCP server.

​
Web UI

Navigate to your Soria instance and you’ll be redirected to the login page if you’re not authenticated. Sign in with your credentials — no additional setup required. The MCP proxy handles authentication automatically. Once you’ve added it to your Claude Code config and the backend is running, Claude Code authenticates through the browser flow on first connection.
No API keys or tokens to manage — the proxy picks up your existing session.

​
MCP via direct HTTP

When connecting directly to the MCP endpoint, use:
For a deployed instance, replace the URL with your deployment’s address:
Claude Code will prompt you to authenticate via browser on first use.

​
Switching environments

The MCP proxy supports switching between environments (local, staging, production, PR previews) without re-authenticating:
See Connecting for full environment switching details.
If you see authentication errors after switching environments, use environment_switch with the local target to reconnect to your local backend, then switch back to the intended environment.