# Authorized applications

> Connect an MCP client to Vigilbase, and review or revoke the applications that have access to your account from Settings in Vigilbase One.

Source: https://docs.vigilbase.com/one/getting-started/authorized-applications

**Authorized applications** lists the MCP clients, such as AI assistants, that you have connected to Vigilbase. You can copy the MCP server endpoint, see which organisation and scopes each application was granted, and revoke access.

Open it from the user menu at the bottom of the sidebar: click **Settings**, then **Authorized applications** under **Connected applications**. It is also at [one.vigilbase.com/settings/authorized-applications](https://one.vigilbase.com/settings/authorized-applications).

## Connect an MCP client

:::steps
1. **Copy the endpoint.** Under **MCP server endpoint**, click the copy button next to `https://mcp.vigilbase.com/mcp`.
2. **Add it to your MCP client.** Follow your client's own instructions for adding a remote MCP server.
3. **Sign in and approve.** Your client opens a secure OAuth flow. You sign in, choose one organisation and approve the scopes the client asks for.
:::

The application then appears in the list. Until you connect one, the page shows **No authorized applications**.

## What each entry shows

- The application's name, with a link to its website if it has one.
- **Organization**: the organisation the access is bound to, and its ID.
- The scopes it was granted, such as **Services · read** or **Billing · read**.
- **Granted**: the date you approved it.

An entry marked **Legacy One connection** was made before sign-in moved to Vigilbase Identity. Reconnect the client through Identity before the transition ends; the entry shows the date when one is set.

## Revoke access

:::steps
1. **Click Revoke** on the application's entry.
2. **Confirm with Revoke access.**
:::

The application's access and refresh tokens stop working straight away, and sessions that authorised renewable access are signed out. To use the client again, connect it again.

## Related

- [Sign in](https://docs.vigilbase.com/one/getting-started/sign-in#manage-your-account) covers your account settings in Vigilbase Identity.