Slack Mcp Server

Created By
jtalk225 months ago
Give Claude full access to your Slack workspace. Read DMs, channels, threads, search messages, and send replies - all with simple browser token auth. No OAuth requirements/rabbit holes.
Overview

What is Slack Mcp Server?

Slack Mcp Server is a tool that allows Claude to interact with your Slack workspace seamlessly, enabling reading and sending messages without the need for OAuth configuration.

How to use Slack Mcp Server?

To use the Slack Mcp Server, add it to your Claude configuration and obtain your browser tokens from Chrome DevTools. Follow the full setup guide available on the GitHub page.

Key features of Slack Mcp Server?

  • Read all DMs and channels effortlessly.
  • Search messages across the entire workspace.
  • Send messages and reply to threads directly from Claude.

Use cases of Slack Mcp Server?

  1. Automating message responses in Slack.
  2. Gathering context by exporting conversation histories.
  3. Managing Slack communications without complex OAuth setups.

FAQ from Slack Mcp Server?

  • Do I need to configure OAuth to use this server?

No, this server works with simple browser token authentication, eliminating the need for OAuth.

  • Can I read all my Slack messages?

Yes, you can browse all DMs and channels, including full conversation histories.

  • Is there a setup guide available?

Yes, a full setup guide is provided on the GitHub page.

Server Config

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ],
      "env": {
        "SLACK_TOKEN": "<YOUR_SLACK_TOKEN>",
        "SLACK_COOKIE": "<YOUR_SLACK_COOKIE>"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
jtalk22
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago