Your client ID
Settings → MCP Server → Connect your AI app shows Your client ID.- It is created automatically the first time an admin opens the page. You do not fill in anything.
- It starts with
vacademy-. - It cannot be removed, so your institute always has a working ID.
- An app that uses it shows your institute’s name when it asks for access.
- It already accepts these sign-in return addresses:
It does not accept the local callbacks that desktop and command-line tools use (Claude Code, Cursor desktop, VS Code). Those need a client ID of their own.
ChatGPT. Newer ChatGPT apps use their own callback address, shown in ChatGPT’s app settings. Let ChatGPT register itself where it can. If you must use a fixed client, an admin copies the callback URL shown in ChatGPT and creates a client ID with it below. Menus and callback formats change; see OpenAI’s auth guide.
Using it in an app
- In the app’s connector form, paste the server URL.
- If the app asks how to register, choose automatic or dynamic registration if it is offered. Otherwise choose your own OAuth client.
- Paste Your client ID into the Client ID field.
- Leave Client secret empty. The server does not issue secrets. It protects the sign-in with PKCE instead, which the MCP standard requires every app to use.
Menus in AI apps change often. For Claude, see Getting started with custom connectors. For ChatGPT, see Connect from ChatGPT. For other apps, see their own MCP or connector documentation.
Add a client ID for another app
Use this for an app whose return address is not in the list above, such as an in-house assistant.1
Open the form
Under Connect your AI app, click Add a client ID for another app.
2
Name it
Enter an App name, for example Marketing team’s assistant. People see this name on the approval screen and in Active connections.
3
Add the redirect URLs
Enter the app’s Redirect URLs, separated by commas (up to 5). The app’s own documentation tells you what to use.
4
Create it
Click Create client ID. The new ID starts with
vcm-. Copy it into the app.Rules for redirect URLs
- Each URL must start with
https://, or behttp://on your own computer (localhost,127.0.0.1or::1). Desktop tools that listen on your computer for the sign-in use the second kind. - Addresses that open an app directly through a custom link (for example
myapp://callback) are not accepted. - The app must send exactly the URL you entered. A different path or a missing slash is refused.
- The URLs are fixed when you create the ID. To change them, create a new client ID and remove the old one.