Skip to main content
Add Raily as a custom plugin so ChatGPT can search your endpoint inside a normal chat. These steps cover self-service custom plugins on ChatGPT web. Availability depends on your plan, role, workspace settings, and rollout. If your workspace uses Apps, ask an administrator or authorized developer to add the same MCP server URL there.

What you need

Before you start, get two things from your Raily administrator:
  • Your connect link. This is the MCP server address for the endpoint you should reach. For Raily-hosted sign-in, the administrator can copy it after granting access. An external provider does not use a Raily user grant.
  • Confirmation of how you sign in. For a Raily-hosted sign-in, use the email address your administrator granted. For a bring-your-own sign-in, use your normal account with that identity provider. A different account may be refused.
You also need access to developer mode, where ChatGPT lets you add custom plugins.

Turn on developer mode

  1. Open Settings, then Security and login.
  2. Switch Developer mode on.
  3. Leave Enforce CSP in developer mode on.
Settings, Security and login, with Developer mode and Enforce CSP in developer mode both on
ChatGPT labels developer mode ELEVATED RISK because custom plugins have not been reviewed. Add only servers that you or your organization control. Keep Enforce CSP in developer mode on so the plugin uses the same restrictions it would have in production. If there is no Developer mode setting, self-service custom plugins may be unavailable for your plan, role, workspace settings, or rollout. On a managed workspace, ask an administrator whether they can enable it or add the endpoint through Apps.

Add the plugin

1

Open Plugins

Select Plugins in the sidebar, then the + at the top right of the page.
2

Name it

Enter a Name and a short Description you will recognize later. The icon is optional.
3

Paste your connect link

Leave Connection on Server URL, and paste your connect link into the field below it.
4

Keep Authentication set to OAuth

Raily identifies you through your sign-in. OAuth is already selected, so do not change it.
5

Confirm the warning

ChatGPT warns that custom MCP servers introduce risk. Read it, then tick I understand and want to continue. Create stays greyed out until you do.
The New Plugin form with the Raily endpoint URL, OAuth authentication, risk confirmation, and Create button
6

Select Create

ChatGPT connects to the server and hands you over to Raily to sign in.
The address field suggests an example ending in /sse. Your Raily connect link ends in /mcp. Paste it as you were given it, and do not change the ending to match the example.
You can check the link before you create anything. Once you paste a working address, the text under Advanced OAuth settings stops asking for a valid MCP server URL and offers to review the settings it found. If it does not change, the link is wrong or the server cannot be reached.
This self-service setup does not roll the plugin out to your workspace. On a managed workspace the Plugins page also has tabs for public plugins and for your workspace, but a workspace-wide rollout is an administrator’s job and is not covered here.

Sign in to Raily

After you select Create, ChatGPT starts the connection. What appears after the first Raily screen depends on the endpoint’s sign-in provider.
1

Start the sign-in

ChatGPT shows Add your plugin name to ChatGPT, with its own notes on permissions and data. Select Sign in with your plugin name.
The ChatGPT sign-in prompt for a Raily plugin, with a Sign in with Raily button
2

Confirm the connection

The first Raily screen is headed Connect ChatGPT to the Organization name shown to users. It lists what ChatGPT will be able to do: view your email address, view your basic profile, and remember the connection. Check the client and Organization, then select Continue. Cancel stops the connection.
The first Raily screen, asking to connect ChatGPT to an Organization, with Continue
3

Continue with the sign-in provider

For a Raily-hosted sign-in, use the granted email address. A different account may be refused.For a bring-your-own sign-in, Raily sends you to the identity provider configured for the endpoint. Use your normal account there and complete any prompt that provider shows. Your provider controls who may continue.
4

Finish a Raily-hosted sign-in

This step appears only for a Raily-hosted sign-in. The second Raily screen shows Signed in as your address and what the plugin will be able to do, including searching your endpoint. If the address is wrong, use Not you? Switch account rather than continuing. Otherwise select Allow access.
The second Raily screen, showing the signed-in address and Allow access
The consent flow lets ChatGPT use the endpoint as your signed-in identity. It does not create or widen a Raily-hosted endpoint grant. Check the Organization name and signed-in account before you continue.

Check the connector

ChatGPT confirms that the plugin is installed and opens its card.
The installed connector card, showing the connection, an empty Actions block and the connection information
Actions says no app actions are available yet. That is normal right after connecting. Select Refresh to scan the server and load its tools. Information shows the address you entered, the authorization used, and the date. Check the address here if you manage more than one endpoint.

Use Raily in a chat

A connected plugin is not automatically active. You choose it for the message you are sending. In the composer, select Plugins in the row under the box, then your Raily plugin. Its name appears in front of your message. Type your question and send it.
The composer with the Raily plugin selected and a question typed, before sending
Choosing the plugin applies to that message. Select it again for your next question.

Check that it works

An installed status confirms that ChatGPT completed setup. It does not confirm that search returns results. Ask a question that your source content answers. Confirm that ChatGPT uses your content rather than general knowledge.
An answer in ChatGPT showing article cards returned by the connected endpoint

Verify your domain for the ChatGPT app directory

This section is for Raily administrators who want to publish an endpoint as an app in OpenAI’s ChatGPT app directory. OpenAI asks you to prove you own the app’s domain by serving a verification token from it. Raily can serve that token for you. OpenAI checks the root of the domain, so the endpoint needs its own address first: a custom domain or a Raily-hosted address. See Give an endpoint its own address. The default Raily address can’t be used for a directory submission.
1

Use the endpoint's own address in your submission

When you submit the app to OpenAI, enter the endpoint’s custom domain or Raily-hosted address as the app’s MCP server URL. OpenAI gives you a verification token.
2

Paste the token in Raily

Open the endpoint in Search Rail. In the Submit to ChatGPT App Directory card, paste the token into Verification token and click Save. The card appears once the endpoint has a custom domain or Raily-hosted address.
3

Check that Raily is serving it

The message under the field changes to say Raily is serving the token. Raily now answers at /.well-known/openai-apps-challenge on the endpoint’s address, for example https://mcp.yourcompany.com/.well-known/openai-apps-challenge. If the card says the endpoint is still updating, wait a moment before you continue.
4

Finish verification with OpenAI

Go back to your submission and run OpenAI’s domain check.
Each endpoint holds one token. If the endpoint has several addresses, they all serve the same token, so submit one of them at a time. To stop serving the token, clear the field and click Save. If Raily refuses the token, check that you copied only the token, with no spaces or line breaks.

Next steps

Connect to Claude

Follow the Claude setup

Add and manage users

Grant Raily-hosted user access