Slack Local MCP

Created By
nqkdev7 months ago
A lightweight Model Context Protocol (MCP) server for Slack automation using cookie-based authentication.
Overview

What is Slack Local MCP?

Slack Local MCP is a lightweight Model Context Protocol (MCP) server designed for automating tasks in Slack using cookie-based authentication, eliminating the need for complex app setups.

How to use Slack Local MCP?

To use Slack Local MCP, install it via npx or manually, configure it with your Slack cookie and workspace URL, and start automating Slack actions using natural language commands.

Key features of Slack Local MCP?

  • Send messages to channels or direct messages.
  • Schedule messages for future delivery.
  • Fetch conversations for AI summarization.
  • Add emoji reactions to messages.

Use cases of Slack Local MCP?

  1. Automating daily team updates by fetching and summarizing messages.
  2. Scheduling reminders for meetings or events.
  3. Managing threads and responding to discussions efficiently.

FAQ from Slack Local MCP?

  • Is Slack Local MCP secure?

Yes, but handle your Slack cookie carefully as it provides full access to your workspace.

  • Can I use it for team-wide automation?

It's designed for personal use; for team deployments, consider OAuth-based solutions.

  • What if my cookie expires?

You will need to extract a new cookie from your browser to continue using the server.

Server Config

{
  "mcpServers": {
    "slack-local": {
      "command": "npx",
      "args": [
        "-y",
        "slack-local-mcp"
      ],
      "env": {
        "SLACK_COOKIE_D": "xoxd-your-cookie-value-here",
        "SLACK_WORKSPACE_URL": "https://your-workspace.slack.com"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
nqkdev
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)

a day ago