Manage MCP apps
As a system administrator, see every AI assistant connected to your platform through MCP in one list, change what it can do or remove it for all users.
Updated on 15 October 2026
Every AI assistant that connects to your platform through MCP, such as ChatGPT, Claude or Copilot Studio, appears in one list, however it was set up. From this list, you can check what each assistant is allowed to do and change it for everyone, without asking users one by one.
The same list, Connected apps, also shows the applications that call the Elium API. This article covers MCP apps. For API applications, see API and connected applications.
Open the list
Click your avatar, choose Settings, then select Advanced > Connected apps.
What the list shows
Each row is one application.
| Column | What it shows |
|---|---|
| Title | The name of the application, its scopes and a DCR badge if the application registered itself. An MCP app has the MCP scope, and MCP (writable) if it can create and edit articles. An application with the API scope calls the Elium API. |
| Redirect URL | The address the application sends users back to after they approve it. A +1 button, or +2 and so on, lists the other addresses. |
| Client ID | The identifier the application uses with OAuth, with a copy button. |
| Client Secret | The secret of the application. Click it to reveal or copy it. An application without a secret shows "No client secret set". |
| Trusted | Yes if users connect without seeing the consent screen. |
An application with the DCR badge was not created by an administrator. It registered itself when someone connected it, as ChatGPT and Copilot Studio do through dynamic client registration. Claude, which uses its published identity, also appears with this badge. Each registration is its own row, so the same assistant can appear several times, for example when several people add it on their side.
The list shows applications, not people. To see which applications can access their own account, each user opens Authorised apps in their personal settings.
Change what an application can do
Open the menu at the end of the row and choose Edit.
-
Scopes: tick or untick MCP and MCP (writable). For example, untick MCP (writable) to make an assistant read-only.
-
Trusted: turn it on only for an application you control. A trusted application skips the consent screen.
-
Title and Redirect URLs: you can change them for an application you registered. For an application with the DCR badge, the application manages them itself.
Click Save. Scope changes apply to tokens issued from then on: users who already connected keep their current permissions until their token is renewed.
The same menu has OAuth details..., with the addresses and identifiers a developer needs to connect the application. To register an application yourself, click New application: see Register an application.
Remove an application for all users
Open the menu at the end of the row, choose Delete, then confirm.
The client ID and secret stop working at once, and every token issued to the application becomes invalid. Everyone who connected it loses access until they connect a replacement.