Skip to main content
Every MCP endpoint needs a sign-in provider. Use Raily-hosted sign-in to grant access by email and choose each person’s endpoints in Raily. Connect your own OpenID Connect provider when your organization manages access in Google, Microsoft Entra ID, Auth0, Okta, Keycloak, or another OIDC provider. Manage providers under Security → Access → Sign-in providers.

Before you begin

You need a paid plan and permission to manage sign-in providers in the selected Organization. Account Owners and Administrators have this permission. A role assigned in a parent Organization also applies in its descendants. For an external provider, you also need permission to create or edit an OIDC web application. Raily shows provider-specific setup instructions. The redirect URI is generated after you attach the provider to an endpoint.
Raily-hosted sign-in does not need external credentials. You manage its users and endpoint grants in Raily.

Choose a provider

Set up Raily-hosted sign-in

Raily creates a hosted sign-in when it creates a new Organization. If the selected Organization does not have one, the provider list shows Set up Raily sign-in.
1

Open Sign-in providers

Go to Security → Access → Sign-in providers. If the selected Organization does not have a hosted provider, the setup banner appears above the provider list.
The Sign-in providers page with the Set up Raily sign-in banner
2

Set up Raily sign-in

Select Set up Raily sign-in and wait for Raily sign-in to appear as Verified and Active.
The provider list after Raily sign-in has been set up, showing Verified and Active status
You can now attach this sign-in to an endpoint and grant people access by email.

Configure an external OIDC provider

Keep Raily and your identity provider open while you work. The wizard shows how to create the OIDC application and where to find its client ID and client secret. You will add the endpoint-specific redirect URI after you attach the provider in Raily.
1

Open the provider wizard

Go to Security → Access → Sign-in providers, then select Configure OAuth Provider.
The Sign-in providers page with the Configure OAuth Provider button
2

Name the configuration

Open Provider and choose your identity provider. If yours is not listed, choose Custom, the last option, to connect any other OpenID Connect provider.
The provider picker with Raily, Google, Azure AD, Auth0, Okta, and Keycloak
Enter an OAuth Client Name, then select Continue. The name only identifies this configuration in Raily.
Basic Information with Google selected, an OAuth client name, and the Continue button
3

Enter the provider credentials

Follow the setup instructions shown for your provider. They list the application type and the values to enter in your provider.
Google OAuth setup instructions with the consent screen and OAuth client application settings
Enter the Issuer URL, Client ID, and Client Secret.For Google, you can upload the credentials JSON file from Google Cloud Console instead. For Microsoft Entra ID, enter your directory’s Tenant ID. Do not use common, organizations, or consumers because Raily cannot verify their placeholder issuer.For Custom, the issuer is the URL your provider serves /.well-known/openid-configuration from. Discover Config fills in the value the provider declares.Raily does not save the client secret in your browser while you work through the wizard. If you leave the wizard and come back, enter the Client Secret again.
Google provider credentials with the issuer URL, client ID, client secret, and Discover Config button
4

Discover the OpenID configuration

Select Discover Config. Raily reads the provider’s OpenID configuration and fills in its authorization and token endpoints. Review the issuer if Raily updates its spelling, then select Continue.
Verify and Save showing the issuer, authorization endpoint, token endpoint, and a successful configuration discovery
5

Review the connection test and save

Raily tests the client credentials automatically when you continue. Confirm that Verify & Save says Connected and that the issuer and endpoints are correct.
Verify and Save showing a successful Connected test for a Google provider
Select Save.
The provider now appears as Verified and Active. Open its row menu and select Test Connection whenever you need to test it again.
A verified and active Google provider with its row menu open, showing Test Connection

Attach the provider to an endpoint

Adding a provider does not change any endpoint until you attach it.
  1. When you create an endpoint, choose the provider under Who can connect. To change an existing endpoint, open it and choose the provider under Security → Sign-in provider.
  2. Select Create Server or Save Changes.
For an external provider, the endpoint page shows 1 step to go live with the endpoint’s redirect URL. Copy it, add it to the allowed callback URLs of the OIDC application in your provider, then select I’ve added it to mark the step done. Each endpoint has its own redirect URL. Raily-hosted sign-in does not need this step.
On an endpoint that uses Raily-hosted sign-in, you can also choose who may start using it: only people you invite, or anyone who signs up. See Open sign-up.
An endpoint page with Google Provider selected and the Redirect URI to register
People must sign in through the attached provider before they can search. Every endpoint needs a provider. Raily does not offer an open endpoint without authentication.

Next steps

Access control

Choose between user grants, external sign-in, and API keys

Add and manage users

Grant endpoints through Raily-hosted sign-in