Skip to main content
Your plug-in

Let only your customers use your plug-in (Clerk sign-in)

Make customers sign in with your own Clerk application before they can use your plug-in in ChatGPT, for a plug-in that is only for your members or existing customers.

Browse all topics

By default anyone who adds your plug-in in ChatGPT can use it. With Clerk sign-in, ChatGPT first opens your own Clerk sign-in page, and your plug-in answers only customers who signed in there. It is included in your plan, and you set it up yourself, from plug-in version 0.16.0.

Before you start

  • A Clerk application of your own (clerk.com), with the customers or members who may use the plug-in as its users.
  • Your plug-in live on test, on version 0.16.0 or later.
  • Your plug-in on version 0.16.0 or later. If its page shows an Upgrade button, press it first: test, then production.

Open the Clerk sign-in panel

Open your plug-in under My plug-ins and open the Integrations tab. Under Who can use your plug-in, press the Clerk sign-in tile. The tile says Set up while sign-in is off and On once your keys are saved. The panel starts with the state: Off, anyone can use your plug-in, or On, with your Clerk instance and the last four characters of your secret key. Below it are four numbered steps.

1. In Clerk, add your plug-in's addresses

  1. 1The panel shows your plug-in's Test and Production addresses, each with a Copy button.
  2. 2In the Clerk Dashboard, open your application and the instance your customers sign in to: Development to try it, Production for real customers.
  3. 3Open Agents, then MCP servers, and press Add MCP server (or Get started the first time).
  4. 4Paste the test address, tick Allow public clients to connect so ChatGPT can register itself, and press Add server. Do the same for the production address.

Clerk then checks each address on its own page. Until your keys are saved in step 2, those checks report that the plug-in does not ask for sign-in yet: that is expected. Press Re-test connection after step 2.

2. Paste the publishable key and save

  1. 1In Clerk, open API keys for the same instance.
  2. 2Copy the Publishable key (pk_test_… or pk_live_…) into the first field. That is all most businesses need: leave Secret key (optional) empty.
  3. 3Only if you switched Clerk to opaque access tokens (OAuth applications, Settings, Access token format), also copy the Secret key (sk_test_… or sk_live_…) into the second field.
  4. 4Press Save. BizPlug checks the keys with Clerk before it saves anything, and shows the result under the form as a list: a green mark for each step that is fine, a red mark for each that is not.
What you see under SaveWhat it means
Saved. Customers now sign in…Sign-in is on, on test and in production at once.
Saved, but one step in the Clerk Dashboard is still missingThe keys are saved and sign-in is on, but Clerk does not let ChatGPT register itself yet. Do step 1 (tick Allow public clients to connect), then press Check sign-in.
These keys could not be used.Nothing was saved. The list says why: Clerk refused the secret key, or the two keys are from different applications or instances.
One key is a test key and the other a live keyUse both keys from the same instance: Development (test) or Production (live). Or leave the secret key empty.

With or without the secret key

Publishable key only (recommended)With the secret key
What BizPlug storesNothing secret: the publishable key and your Clerk address.Also the secret key, encrypted.
How a sign-in is checkedWith your instance's public signing keys, on BizPlug's server, on every request.By asking your Clerk application, on every request.
Clerk access token formatJWT access tokens (Clerk's default).JWT or opaque.
Removing a customer's accessTakes effect when their access token expires, usually within minutes.With opaque tokens, at once.

3. Check sign-in

Press Check sign-in. It checks your Clerk instance, that the secret key works and belongs to the same instance as the publishable key, and, for your test and production plug-in, that it runs a version that asks for sign-in. It sends nothing to anyone, and the last result stays on the panel.

4. Add your plug-in again in ChatGPT

In ChatGPT, remove the old connector and create it again with the same address. ChatGPT now shows a Sign in button that opens your Clerk sign-in page, with your application's name. Sign in with a user of your Clerk application and allow access: the plug-in then works as before, with the same menu, answers and requests. Customers who added your plug-in before sign-in was on do the same. Who may sign in is up to you, in Clerk.

Switch it off

Save both key fields empty. Your plug-in is open to anyone again at once, and the tile goes back to Set up. The privacy policy says what BizPlug does with a customer's sign-in: it checks it with your Clerk application on every request and keeps none of their account details.

Last reviewed 21 November 2026

Was this page helpful?