Demo Environment

User Registration

This is an open demo environment. Registration creates a real account with a WebAuthn passkey bound to your device. WebAuthn passkeys are the default authentication mechanism — the library itself can act as the identity provider, or optionally integrate with enterprise SSO providers during implementation. Emails are not enabled in this demo environment.

How Registration Works

This platform uses WebAuthn passkeys for passwordless authentication — the same standard used by Apple, Google, and Microsoft for phishing-resistant sign-in.

1You provide your name, email, and role below
2Your browser generates a public/private key pair bound to this domain. The private key stays on your device (or in your password manager). No passwords are created or stored.
3The server stores only the public key and issues an OAuth 2.0 session token via PKCE
4You are signed in automatically

Enterprise Integration Options

The library can act as the identity provider using WebAuthn passkeys, or optionally integrate with enterprise identity infrastructure during implementation. There are many options available:

SAML 2.0 / OpenID Connect

Optionally redirect authentication to your IdP (Okta, Azure AD, Google Workspace). The platform receives a signed assertion with the user's identity and roles.

SCIM Directory Sync

Users and groups can be automatically provisioned and deprovisioned from your corporate directory. When someone joins, they appear here. When they leave, access is revoked immediately.

Just-in-Time (JIT) Provisioning

On first SSO login, accounts are created automatically with roles derived from IdP group memberships. No pre-provisioning required.

Passkeys + SSO

WebAuthn passkeys complement SSO as a device-binding factor, adding phishing-resistant MFA on top of your IdP authentication.

MCP Server Integration

After registration, users can connect MCP (Model Context Protocol) servers that extend Claude's capabilities with external tools and data sources. MCP servers authenticate via API keys stored in encrypted per-user secrets. Each server exposes tool endpoints that Claude can call during conversations, enabling integration with your existing infrastructure — databases, APIs, internal services — all governed by per-user permissions and audit logging.