---
title: "Admin approval for apps with MCP servers"
summary: "The installation experience for users depends on whether the workspace requires admin approval for apps."
url: "https://docs.slack.dev/ai/slackbot-mcp-client/admin-approval"
type: "guide"
---

Source: https://docs.slack.dev/ai/slackbot-mcp-client/admin-approval

# Admin approval for apps with MCP servers

The installation experience for users depends on whether the workspace requires admin approval for apps.

## Without admin approval required {#install-no-admin-approval}

When admin approval is not required, workspace members can install the app directly. During installation, they see a consent screen that includes the app's requested permissions and any **External MCP servers** the app connects to.

![The app installation consent screen showing Review app permissions with an External MCP servers section listing server URLs](https://a.slack-edge.com/384d6cf/img/api/partner_docs/mcp_client/user_approving_app_non_admin_approval_required.png)

The workspace member reviews the permissions and MCP server URLs, then clicks **Install** to complete the process.

## With admin approval required {#install-admin-approval}

When the workspace requires admin approval, the app appears in the admin's **Requests** queue. Admins can approve or restrict the app from the [Slack Marketplace management page](https://slack.com/apps/manage).

![The admin Requests page in the Slack Marketplace showing Approve and Restrict options for pending apps](https://a.slack-edge.com/384d6cf/img/api/partner_docs/mcp_client/admin_app_approval_with_mcp_step1.png)

When approving, the admin sees the full list of requested scopes along with a **Connected MCP Servers** section. Each MCP server can be individually allowed or denied.

![The admin approval dialog showing OAuth scopes and a Connected MCP Servers section with Allow checkboxes for each server](https://a.slack-edge.com/384d6cf/img/api/partner_docs/mcp_client/admin_app_approval_with_mcp_step2.png)

## Reviewing installed MCP servers {#admin-review}

After an app is installed, admins can review its MCP server connections at any time from the admin dashboard under **Integrations** > **Installed apps**. The app's detail page shows a **Connected MCP Servers** section with the status of each server (ALLOWED or INACTIVE).

![The admin dashboard showing an installed app with Connected MCP Servers listed with ALLOWED and INACTIVE statuses](https://a.slack-edge.com/384d6cf/img/api/partner_docs/mcp_client/admin_review_external_mcp_server.png)

## Admin access controls {#admin-access-controls}

Admins can control which MCP servers are available in their workspace, and who within that workspace can access them.

When an admin approves an app with the `mcp:connect` scope, access is granted to its declared servers. Re-approval is required if an MCP server from a different domain is added to the app. Only after admin approval will the MCP server appear in Slackbot for users to connect and use.

Admins can also configure who has access to the app, and those same permissions apply to its MCP servers automatically.