MCP connectorsSlack

Slack MCP: connect Slack to Claude and ChatGPT

Ask Claude or ChatGPT what was decided in #pricing last week, who answered the customer in the support thread or where the launch date was set. The answer comes from Slack, with a permalink to every message it relies on.

With Deployed OS everyone connects with their own Slack account. The AI searches the messages that person can see, and it posts only when they ask and have confirmed the channel and the exact text.

4 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Slack in Claude and ChatGPT

Management

Catch up after a week away

Ask what happened in #sales, #product and #leadership while you were off. Decisions, open questions and who owns what, with links to the messages.

Product

Find the decision, not just the thread

Search for where the pricing change or the launch date was agreed and read the whole thread. No more scrolling three weeks back.

Customer support

Answer with what the team already knows

Search #support and the customer channels for how a similar issue was solved, and get the reply drafted in the same chat.

Project management

Post the update where people read it

Write the weekly status in the chat, check it, and the AI posts it to #project-atlas as you. Company guardrails apply to what is posted.

Examples

Ask it like this

“What did we decide about the pricing change in #pricing last week? Link the messages.”
“Summarise the thread in #support about the Acme login issue and tell me if it was solved.”
“Which channels about the Atlas project am I not a member of yet?”
“Search Slack for everything Maria said about the Q3 campaign budget.”
“What has happened in #sales-nordics since Monday? Give me the five things I need to know.”
“Post in #project-atlas: Design review moved to Thursday at 10. Agenda in the thread.”

The connector

What the Slack MCP connector does today

Readsslack_search_messages
Searches the messages you can see, as you: channel, author, text, time and a permalink for each match, newest first.
Readsslack_list_channels
Lists the public and private channels you can see, filtered by a word if you like, with topic, purpose and whether you are a member.
Readsslack_read_channel
Reads the latest messages in a channel you are in, newest first, and further back when you ask.
Readsslack_read_thread
Reads a thread: the first message and its replies.
Writesslack_post_message
Posts a message to a channel or thread as you, once you have confirmed the channel and the exact text. Company guardrails apply.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Reads channels, posts as you: The connector searches messages, lists the public and private channels you can see and reads the channels you are in, with their threads. It can post to a channel or thread as you, and only for people with Edit access.
Each person’s own Slack account: Everyone connects their own Slack account. There is no bot: a private channel you are not in stays closed, and every post carries your name.
You choose who gets it: Admins decide which groups get the Slack connector, and which of those may post. Everyone else never sees it.
Every call logged: Who asked, which connector, when. Deployed OS shows reads and writes per connector and per person, and the log can be exported.

Setup

Set up the Slack connector in three steps

An admin opens Slack’s app page from Deployed OS with the redirect URL and user scopes already filled in, picks your workspace and clicks Create. Your company owns the app, not us.

The admin copies the app’s Client ID and Client Secret into Deployed OS and chooses which groups get Slack. If your workspace requires approval for new apps, approve it there.

Each person connects their own Slack account. From then on they just ask.

Compared

Slack’s own MCP server or Deployed OS?

Slack runs its own MCP server, hosted at mcp.slack.com. People sign in with OAuth from supported AI tools such as Claude, and workspace admins approve which MCP clients may connect. It searches, reads and posts, and works with canvases too. For one person who wants Slack in their AI tool, it is a good fit.

Deployed OS is for the whole company. Slack is one connection next to your CRM, files and other tools, each person is on their own account, admins choose which groups get Slack and who may post, and every call is logged. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.

Their documentation: Slack’s MCP server

Questions

Slack MCP: common questions

Yes. Slack runs its own MCP server, and it works well for one person in a supported AI tool. Deployed OS gives the whole company one Slack connector next to its other tools, with each person’s own account, access per group and a log of every call.

Yes, as you, to a channel or a thread, and only after you have confirmed the channel and the exact text. Only groups with Edit access can post, and company guardrails apply. It cannot edit, delete or react to messages. If you need more, we can extend it for you.

Yes. Deployed OS is your company’s own MCP, so the same Slack connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.

No. The Slack app has user scopes only, so the AI acts as the person asking. It sees the channels they see, and nobody has to invite a bot into a channel.

Yes, the private channels you are a member of, just as in Slack. Channels you are not in stay closed to the AI as well.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors

Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

You’ll hear from Poyan Karimi

Co-founder · Deployed AI