Introduction

Managing connections

The MCP Server page in the Ada dashboard (Platform > MCP Server) shows every AI assistant connection authorized for your instance and lets admins revoke access at any time.

Viewing connections

When someone authorizes access from their AI assistant using OAuth, their connection appears in Platform > MCP Server. Each connection shows the AI assistant application (for example, Claude or Cursor), the date and time it was authorized, and the email of the person who authorized it.

The MCP Server page listing authorized AI assistant connections, each with its application name, creation date and time, and the email of the person who authorized it.

The list appears once at least one connection is authorized. A person who connects more than one AI assistant appears once per application, so each assistant’s access can be managed on its own.

The MCP Server page lists OAuth connections only. API key access is not shown here, because it is not tied to an individual OAuth session.

Revoking a connection

Revoking a connection stops that AI assistant from using the MCP Server. Its current session keeps working for up to 5 minutes, until the session token expires; after that, access stops. To restore access, the person must authorize again.

Revoking affects only the selected application. If the same person has other AI assistants connected, those keep their access.

1

Open the MCP Server page

In the Ada dashboard, go to Platform > MCP Server.

2

Find the connection

Find the connection you want to revoke by its application and the person’s email.

3

Revoke access

Choose Revoke, then confirm. The AI assistant loses MCP Server access within 5 minutes.

Revoking a connection affects OAuth access only. API key access is managed separately on the Platform > API Keys page — see Authentication for details on the two methods and how each is managed.