# 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.

Online: https://mcpforgtm.com/toolkit/it-approval/slack

- Server URL: https://mcp.slack.com/mcp (Source: StackMCP listing, https://mcpforgtm.com/tools/slack)
- Access: Read + write (Source: https://docs.slack.dev/ai/slack-mcp-server)
- Sign-in: Confidential OAuth (registered Slack app) (Source: StackMCP listing, https://mcpforgtm.com/tools/slack)
- Admin approval: Yes (Source: https://docs.slack.dev/ai/slack-mcp-server)
- Setup: Needs admin or IT (Source: https://docs.slack.dev/ai/slack-mcp-server/connect-to-claude)
- 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
(Source: https://docs.slack.dev/ai/slack-mcp-server)

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

## What can it read, and what can it change?

Read + write. Things it can do in your Slack account (Source: https://docs.slack.dev/ai/slack-mcp-server):

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

## 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) (Source: StackMCP listing, https://mcpforgtm.com/tools/slack)

- Each person goes through Slack's OAuth consent screen and authorizes the app. (Source: https://docs.slack.dev/ai/slack-mcp-server)

## Does an admin need to approve it?

What Slack's docs confirm about admin controls:

- An admin must approve or enable the connection: Yes (Source: https://docs.slack.dev/ai/slack-mcp-server)
- Scopes or permissions can limit what it reaches: Yes (Source: https://docs.slack.dev/ai/slack-mcp-server)
- Individual tools can be turned off: Not confirmed
- MCP activity shows in an audit log: Yes (Source: https://docs.slack.dev/ai/slack-mcp-server)

- Workspace admins can approve and manage all MCP client integrations. (Source: https://docs.slack.dev/ai/slack-mcp-server)
- It uses Slack's standard app approval process. (Source: https://docs.slack.dev/ai/slack-mcp-server)
- 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: https://docs.slack.dev/ai/slack-mcp-server, https://docs.slack.dev/reference/audit-logs-api/methods-actions-reference/)

## 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: https://slack.com/help/articles/360003125231-Remove-apps-and-custom-integrations-from-your-workspace)
- The same article says that if app approval is on, only Workspace Owners and app managers can remove apps. (Source: https://slack.com/help/articles/360003125231-Remove-apps-and-custom-integrations-from-your-workspace)

### 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: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp)
- For other assistants, check that assistant's settings or ask your admin.

## Does it use credits or quota?

Not confirmed

## Send this to IT

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

```text
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._