Slack MCP Server logo

Slack MCP Server

by jtalk22

Read, search, summarize, and update Slack conversations through local MCP tools using an existing Chrome session.

Install Slack MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jtalk22-slack-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 19 tools correctly (1mo ago).

Overview

jtalk22/slack-mcp-server MCP server exposes Slack reads, searches, conversation exports, workflow tools, and guarded write actions over local stdio. It uses the Slack session already stored in Chrome rather than requiring a Slack OAuth app or admin approval, then manages rotating session credentials with health checks and refresh support. Reach for it when an agent needs workspace context from DMs, channels, threads, unread messages, or user records. Hosted-only semantic search, catch-up, and triage features require Vectorize and Workers AI, with a free usage tier and a paid unlimited plan.

Use cases

  • Read unread Slack messages and threads
  • Search a workspace for prior discussions
  • Export complete channel or DM histories
  • Send approved replies and manage reactions
  • Run structured incident or support catch-ups

Key features

  • Slack channel, DM, and thread access
  • Workspace message and user search
  • Conversation export with resolved user names
  • Token health checks and Chrome-session refresh
  • Message sending, reactions, and read-state updates
  • Workflow profiles with hosted catch-up and triage

Tools19

What Slack MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/18 checks healthy over the last 76d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @jtalk22/slack-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars32Stargazers on the source repository.
npm downloads2.5kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed19Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Slack MCP Server works

What jtalk22/slack-mcp-server does

jtalk22/slack-mcp-server MCP server gives an MCP client access to Slack conversations and workspace users through a focused local tool surface. It can list channels and DMs, retrieve channel or direct-message history, include thread replies, search messages, resolve user names, inspect unread conversations, and export a complete conversation to a file. The write operations cover sending messages, adding or removing reactions, and marking a conversation as read.

Workflow tools add a local profile layer. Profiles are stored in ~/.slack-mcp-workflows.json and can associate a workflow type with channels, priority people, retention behavior, and summary cadence. Supported workflow kinds include support inboxes, incident rooms, executive briefs, product launch watches, and custom profiles.

How it works

The local path runs over stdio and uses the Slack identity already present in Chrome. Setup reads the newest Slack xoxc- token from Chrome’s LevelDB, snapshots the cookie database and its WAL files, retrieves Chrome Safe Storage from the macOS Keychain, and decrypts the cookies locally. The material says this process does not transmit the extracted credentials; the server communicates with Slack.

Credential storage can use automatic selection, Keychain-only storage, or files. The server supports token health checks, refresh coordination, atomic writes, profile isolation, and fallback to the last known good in-memory credentials when persistence is temporarily unavailable. slack_refresh_tokens extracts refreshed credentials from Chrome and requires a Slack tab to be open there. Request pacing can be controlled with SLACK_MCP_MIN_REQUEST_INTERVAL_MS and SLACK_MCP_MAX_CONCURRENCY.

Setup and configuration

Install and run setup with:

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

The project is intended for Claude Desktop, Cursor, Windsurf, Claude Code, and other stdio MCP clients. No Slack app or admin request is required for this local session-based path, but it acts with the permissions of the signed-in Slack identity.

Tools and capabilities

The jtalk22/slack-mcp-server MCP server includes tools for:

  • Checking token health, authentication state, refresh status, and cache statistics.
  • Listing conversations, reading histories, retrieving threads, exporting full histories, and finding unread channels or DMs.
  • Searching messages and searching workspace users by partial name, display name, or email.
  • Inspecting user details and marking conversations read.
  • Sending messages and managing reactions.
  • Saving and listing workflow profiles.

Three hosted-only tools extend the local features: slack_smart_search provides hybrid semantic and lexical search over indexed history; slack_catch_me_up produces structured workflow-specific catch-up output; and slack_triage classifies and routes threads. These hosted tools require Vectorize and Workers AI. Their free tier includes 25 AI tool calls per month, shared across hosted AI tools; Pro is listed at $19 per month for unlimited use.

Limitations and notes

Browser-session authentication is not the same as a sanctioned OAuth integration. Enterprise Grid may detect this access pattern and terminate the session; the material recommends hosted OAuth or Slack’s official MCP for Grid deployments. The local server cannot access channels unavailable to the signed-in user or act as another user. Workspace retention, DLP, compliance export, and audit controls still apply.

The hosted workflow features are separate from the local JSON profile primitives and are not available solely from the local tool process. Review the repository code and workspace policies before using a browser-session credential method.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Slack MCP Server

Run `npx -y @jtalk22/slack-mcp --setup`, then configure the resulting local stdio server in an MCP client.

Yes. The repository lists Claude Desktop as a compatible client.

The local setup uses the existing Slack session in Chrome and does not require a Slack app or admin request.

It extracts session credentials from Chrome’s stored Slack session, using Chrome storage and macOS Keychain data during setup.

Yes, through the hosted-only `slack_smart_search` tool, which requires Vectorize and Workers AI.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSlack MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jtalk22-slack-mcp-server?style=directory)](https://allmcps.com/mcp/jtalk22-slack-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/jtalk22-slack-mcp-server"><img src="https://allmcps.com/api/badge/jtalk22-slack-mcp-server?style=directory" alt="Slack MCP Server on AllMCPs" /></a>