Slack MCP Server

Name: Slack MCP Server
Author: jtalk22

by jtalk22version 5.2.1i★ –iComputer or cloud

Registry nameio.github.jtalk22/slack-mcp-server

Install

Overview

Description from the maker (original English)

Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Chat & email
You need to fill in: SLACK_TOKEN, SLACK_COOKIE

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: SLACK_TOKEN, SLACK_COOKIE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.revasserlabs.com/oauth/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ],
      "env": {
        "SLACK_TOKEN": "your-value",
        "SLACK_COOKIE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http slack https://mcp.revasserlabs.com/oauth/mcp

Or run it on your computer

claude mcp add slack --env SLACK_TOKEN=your-value --env SLACK_COOKIE=your-value -- npx -y @jtalk22/slack-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.revasserlabs.com/oauth/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ],
      "env": {
        "SLACK_TOKEN": "your-value",
        "SLACK_COOKIE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "slack": {
      "type": "http",
      "url": "https://mcp.revasserlabs.com/oauth/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "slack": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ],
      "env": {
        "SLACK_TOKEN": "your-value",
        "SLACK_COOKIE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.revasserlabs.com/oauth/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SLACK_TOKEN secret env
Slack xoxc- token from browser session
SLACK_COOKIE secret env
Slack xoxd- cookie from browser session

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account jtalk22, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 72 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1783 servers in this category
Published to the registry more recently than 86% of the other 1783 servers in this category
Basic checks equal to or better than 100% of the other 1783 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Slack MCP Server safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SLACK_TOKEN, SLACK_COOKIE

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (5.2.1) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Slack MCP Server

Catch up on Slack without reading it.

Unreads, threads, and search — in your agent’s context, from the session you already have.

Set it up, then register it with your client.

npx -y @jtalk22/slack-mcp --setup

claude mcp add slack -- npx -y @jtalk22/slack-mcp

Check where your credentials are stored and how old they are, or run it read-only so your agent can read Slack but never post.

npx -y @jtalk22/slack-mcp --doctor --security

npx -y @jtalk22/slack-mcp --read-only

On Enterprise Grid, Slack can end a session it sees being automated. Use Slack's official MCP server there.

Claude Code Claude Desktop Cursor Copilot Windsurf Gemini CLI Codex CLI any stdio MCP client

What’s new in 5.1 · ▶ the whole morning in three minutes · interactive walkthrough · setup guide

If your workspace is on Slack's free plan

Checked against Slack's published plans and pricing on 2026-10-07.

A free workspace keeps 90 days of message history, allows 10 app integrations, and gets only Slack's basic AI. The AI people actually want — AI search across the workspace, channel recaps, Slackbot acting as an agent, AI workflow generation — starts on Business+ at $15 per user per month on annual billing ($18 month to month). Pro, at $7.25, buys unlimited history and unlimited apps, not the advanced AI. So a ten-person free workspace that wants an AI it can ask about its own Slack is looking at $1,800 a year, and the cheaper upgrade does not get them there.

This package gives that workspace an agent over the same Slack for nothing, running on the AI subscription its people already pay for. Three things follow from how it works:

It installs no Slack app, so it uses none of your 10 app slots. If your workspace is already at the cap, this is the only way left to add an integration at all.
It needs no admin approval, because it is not an app anyone has to approve. It reads Slack through your own browser session, with exactly the access you already have and nothing more.
It can export what you can still see. On a free plan, history older than 90 days stops being reachable — Slack's own free export covers public channels only and is admin-only, so DMs and private channels are not in it. slack_get_full_conversation writes them out with their threads while they are still inside the window. It cannot retrieve anything already past the line; nothing can.

The browser-session route is not a workaround to apologise for. For a workspace Slack's own AI does not serve, it is the only route there is.

Two ways into Slack

Slack's official MCP server is an app your workspace admin approves and controls. Use it when your organisation wants a sanctioned integration. This server uses the browser session already in Chrome instead, so there is no app to install and no admin to ask, and it runs as a local command for any stdio MCP client. It acts as you, with exactly your access.

Side by side: the managed integration path vs. the local session path

	Slack official MCP	Slack MCP Server — local
Starting point	A Slack-managed remote integration	The Slack session already in Chrome
Workspace control	Governed by workspace integration settings	No Slack app or admin request for the local path
Transport	Streamable HTTP	Local stdio
Client surface	Slack's supported partner integrations	Any stdio MCP client
Authentication	OAuth	Existing browser session
Credential lifetime	Managed OAuth	Rotating session with health checks and refresh
Product surface	Broad Slack-native capabilities	20 tools across read, act, and automate
Protocol	Slack-managed	MCP 2026-07-28 and every 2025 revision, from the same binary
Runtime	Slack-managed	MIT code on your machine

Is the local path against Slack's terms?

Treat browser-session automation as an acceptable-use decision for you and your workspace. The server acts as your signed-in Slack identity and cannot read a channel you cannot read or act as another user. It does not evade server-side retention, DLP, compliance exports, or audit controls.

"No admin request" means there is no Slack app installation to approve. It does not mean workspace activity disappears from Slack's systems. If your policy requires a sanctioned integration, use Slack's official MCP server.

Install

Node 22 or 24 recommended. Node 20+ is supported and CI-tested.

npx -y @jtalk22/slack-mcp --setup

Prefer a persistent CLI: npm install -g @jtalk22/slack-mcp then slack-mcp --setup.

Then:

Copy the stdio command --setup prints when it finishes.
Paste it into your client, or run the claude mcp add line it prints.
Fully restart the client.
Ask the agent to run slack_health_check.
A workspace name in the response means the connection is live.

Per-client configuration keys are in the setup guide.

Use the same server command everywhere:

"command": "npx", "args": ["-y", "@jtalk22/slack-mcp"] }

On macOS, setup can extract from Chrome and persist the selected storage backend. On other platforms, provide SLACK_TOKEN and SLACK_COOKIE through the client's environment configuration. Docker, HTTP, and detailed client examples live in docs/SETUP.md and docs/DEPLOYMENT-MODES.md.

Client configuration matrix

Client	Configuration surface	Status
Claude Code	`claude mcp add` or `~/.claude.json`	Documented
Claude Desktop	Desktop MCP configuration	Verified
Cursor	`.cursor/mcp.json`	Documented
GitHub Copilot	`.vscode/mcp.json`	Documented
Windsurf	`~/.codeium/windsurf/mcp_config.json`	Documented
Gemini CLI	`~/.gemini/settings.json`	Documented
Codex CLI	`codex mcp add` or `~/.codex/config.toml`	Documented
Other clients	Any stdio MCP configuration	Protocol-compatible

20 tools: read, act, automate

Read channels, DMs, threads and search; act with a reply, a reaction or a read-state change; run the catch-up and typed workflows locally. The surface is 20 tools today: 13 read-only operations, 4 write-path tools that each carry an MCP destructive annotation so clients can gate workspace writes, and 3 local workflow tools. One of the reads is slack_session_report, which reads nothing from Slack: it returns what this process has done, as counts. Every tool does its work here — reads Slack or local state — and none is a placeholder for something you would have to pay for. Four read tools accept include_rich_message_fields: true to surface attachments, blocks, files, reactions, and metadata—complete inputs and response contracts live in docs/API.md.

Speaks MCP 2026-07-28 and every 2025 revision from the same binary — era-negotiated over stdio, stateless per request over HTTP (no Mcp-Session-Id; GET/DELETE answer 405). The claim is a test, not a sentence: test/mcp-era.test.js drives the real SDK client at both eras against the real entry points.

Advertising fewer tools. Every tool the server advertises sends its schema to the model on every turn, before you ask anything. SLACK_MCP_TOOLS=essentials advertises six (unread, history, search, thread, user lookup, send); SLACK_MCP_TOOLS=read the 13 read-only operations; --tools=slack_x,slack_y an explicit set. The default is all 20. Filtering changes what is advertised, not what is callable.

The full tool inventory

13 read-only operations

Tool	Purpose
`slack_health_check`	Verify credentials and workspace identity
`slack_token_status`	Inspect credential age, health, cache, profile, and storage state
`slack_refresh_tokens`	Refresh local credentials from the browser session on macOS—reads Slack, writes only local state
`slack_list_conversations`	List channels and DMs
`slack_conversations_history`	Read channel or DM history with optional rich fields
`slack_get_full_conversation`	Export complete history and threads
`slack_search_messages`	Search across the workspace
`slack_get_thread`	Read all replies in a thread
`slack_users_info`	Resolve a user

Only the beginning is shown; read the rest in the repo

Slack MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

If your workspace is on Slack's free plan

Two ways into Slack

Install

20 tools: read, act, automate

13 read-only operations