Sign-in and access
How your users sign in, who is an admin, and how to connect MCP clients.
Your company login today
Today a self-hosted install signs users in through River Logic's hosted sign-in service (WorkOS). Your identity provider is connected to it as a single sign-on connection, over SAML 2.0 or OpenID Connect, so your users sign in with their company login.
The four sign-in fields on the install form come from that connection. River Logic creates them and gives them to you:
| Field | What it is |
|---|---|
| SignInClientId | The ID of eode's sign-in application |
| SignInDomain | The sign-in page your users' browsers are sent to, and where MCP sign-in tokens come from |
| SignInApiKey | The key eode-app uses to call the sign-in service |
| SignInWebhookSecret | Signs the sign-in service's calls back to eode-app, so they can be verified |
Your users' identities and organization memberships are held by the sign-in service.
Your own identity provider, directly
Signing users in with your own identity provider directly, with no River Logic service in the path, is in development. This page will cover the setup when it's available.
Admins and organizations
Admins manage members and roles from Organization in eode (Organization).
Connect an MCP client
Your MCP endpoint is https://MCP_HOST/mcp. Clients sign in with OAuth: an MCP client that supports it finds the
sign-in from the endpoint by itself.
- Claude: add a custom connector with that URL.
- Microsoft Copilot: add it as an MCP connector.