Toolkit / IT approval kit / Slack

Slack connector: IT approval one-pager

Slack's MCP server can read and change data. An admin or IT has to act before anyone can connect it. This page covers what it can reach and change, how it signs in, who approves it and how to turn it off.

Download (.md) Print this page

Server URL

https://mcp.slack.com/mcp Source: StackMCP listing, checked 2026-10-16

Access

Read + write

Source: docs.slack.dev, checked 2026-10-16

Sign-in

Confidential OAuth (registered Slack app) Source: StackMCP listing, checked 2026-10-16

Admin approval

YesSource: docs.slack.dev, checked 2026-10-16

Setup

Needs admin or IT

An admin or IT has to act first, for example by approving or enabling the integration. Don't plan on connecting it alone. Source: docs.slack.dev, checked 2026-10-16

Credits

Credits not confirmed

Plan

Not confirmed

What data can it reach?

Slack's docs list these tools for its MCP server:

• search messages/files/users/channels
• send/schedule messages
• canvases
• lists
• file upload
• reactions

• It can search messages and files and read what's in them. Source: docs.slack.dev, checked 2026-10-22
• It can search public and private channels. Source: docs.slack.dev, checked 2026-10-22
• It can read full user profiles, including custom fields and statuses. Source: docs.slack.dev, checked 2026-10-22
• Each tool needs specific OAuth scopes (permissions) on the person's user token. Slack lists the scopes for each tool. Source: docs.slack.dev, checked 2026-10-22

What can it read, and what can it change?

Read + write Some Slack MCP tools change data, not just read it.

Things it can do in your Slack account:

• sends and schedules messages
• creates channels and conversations
• adds emoji reactions
• creates and updates canvases
• uploads files
• creates and updates lists and list records

Review each change before you approve it, especially anything that sends messages or edits records other people rely on.

Which actions should wait for a person's OK?

Have a person approve each change listed above before it runs. Every StackMCP recipe follows this rule: read freely, but create, change or send only after you approve it.

How does it sign in?

Sign-in method (from the StackMCP listing): Confidential OAuth (registered Slack app)

• Each person goes through Slack's OAuth consent screen and authorizes the app. Source: docs.slack.dev, checked 2026-10-22

Does an admin need to approve it?

What Slack's docs confirm about admin controls:

• An admin must approve or enable the connectionYesSource: docs.slack.dev, checked 2026-10-16
• Scopes or permissions can limit what it reachesYesSource: docs.slack.dev, checked 2026-10-16
• Individual tools can be turned offNot confirmed
• MCP activity shows in an audit logYesSource: docs.slack.dev, checked 2026-10-16

• Workspace admins can approve and manage all MCP client integrations. Source: docs.slack.dev, checked 2026-10-22
• It uses Slack's standard app approval process. Source: docs.slack.dev, checked 2026-10-22
• Slack's audit logs record MCP tool calls, for example when an AI app reads a channel or sends a message for a person. Source: docs.slack.dev, checked 2026-10-22 Source: docs.slack.dev, checked 2026-10-22

How do we turn it off?

In Slack

• These steps come from Slack's general help on removing apps, not from MCP-specific help. To revoke one person's authorization, go to Authorizations, find Authorized members, click See all, then click Revoke. The same article explains how to remove the app from the workspace. Source: slack.com, checked 2026-10-22
• The same article says that if app approval is on, only Workspace Owners and app managers can remove apps. Source: slack.com, checked 2026-10-22

In the AI assistant

• In Claude, you can revoke access at any time. Disconnect the connector in Claude's settings, or in the tool's own security settings. Source: support.claude.com, checked 2026-10-22
• For other assistants, check that assistant's settings or ask your admin.

Does it use credits or quota?

Not confirmed Slack's docs don't say whether MCP calls use credits or paid usage.

Send this to IT

Copy this, fill in the parts in [brackets] and send it.

Subject: Request: connect Slack to [your AI assistant] for my sales work

Hi [name],

I'd like to connect Slack to [your AI assistant] using Slack's official MCP connector. I want to use it for [task, for example call prep or pipeline review].

What I'm asking for:
- Approval for the app through Slack's standard app approval. Then I can authorize it for my own account on Slack's OAuth consent screen.
- Any admin step Slack needs before I can connect.

How I'll use it:
- I'll approve each action that creates, changes or sends something before it runs.
- I'll disconnect it if you ask, or when I stop using it.

Quick facts:
- Access: Read + write
- Sign-in: Confidential OAuth (registered Slack app)
- Setup: Needs admin or IT
- Credits: Not confirmed

The facts and their sources: https://mcpforgtm.com/toolkit/it-approval/slack

Thanks,
[your name]

Each fact links to its source: the tool vendor's docs, the AI assistant's docs or the StackMCP listing. Anything without a source says Not confirmed. Vendors change their connectors, so confirm anything important on the linked page. We last checked the quotes on this page (vendor docs and the Claude help article) on Oct 22, 2026, and the StackMCP listing facts on Oct 16, 2026.

All the facts on one page, with sources: Slack MCP server. Setup steps: Connect Slack.

Other one-pagers: HubSpot · Salesforce · Gong · Apollo

Something out of date on this page? Report a correction, with a link to the vendor page that shows the right information.