Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

An MCP server that connects to Slack via Socket Mode (WebSocket) and surfaces real-time message notifications through MCP tools. No public URL or ngrok needed.

README.md

Slack Notifier MCP Server

An MCP server that connects to Slack via Socket Mode (WebSocket) and surfaces real-time message notifications through MCP tools. No public URL or ngrok needed.

How It Works

This server runs two things simultaneously in a single process:

  1. Slack Socket Mode client — connects outbound to Slack over WebSocket and receives events in real time
  2. MCP server (stdio) — exposes tools to query, filter, and manage those notifications

When someone posts a message in Slack, the Socket Mode connection pushes the event to your server. The server stores it in memory (with optional disk persistence), and you can query it via the MCP tools.

Setup

1. Create a Slack App

  1. Go to api.slack.com/apps and click Create New AppFrom scratch
  2. Name it something like "Message Notifier" and pick your workspace

2. Enable Socket Mode

  1. Go to SettingsSocket Mode and toggle it On
  2. You'll be prompted to create an App-Level Token — name it something like "socket-mode-token"
  3. Give it the connections:write scope
  4. Copy the token (starts with xapp-) — this is your SLACK_APP_TOKEN

3. Subscribe to Events

  1. Go to FeaturesEvent Subscriptions and toggle it On
  2. Under Subscribe to bot events, add:
  • message.channels — messages in public channels
  • message.groups — messages in private channels
  • message.im — direct messages
  • message.mpim — group direct messages
  1. Save changes

4. Add Bot Token Scopes

  1. Go to FeaturesOAuth & Permissions
  2. Under Bot Token Scopes, add:
  • channels:history — read messages in public channels
  • groups:history — read messages in private channels
  • im:history — read direct messages
  • mpim:history — read group DMs
  1. Install (or reinstall) the app to your workspace

5. Invite the Bot

Invite your bot to the channels you want to monitor: `` /invite @Message Notifier ``

6. Configure the MCP Server

Add this to your Claude Desktop / Claude Code MCP config:

{
  "mcpServers": {
    "slack-notifier": {
      "command": "node",
      "args": ["/path/to/slack-notifier-mcp-server/dist/index.js"],
      "env": {
        "SLACK_APP_TOKEN": "xapp-1-your-token-here",
        "PERSIST_PATH": "/path/to/notifications.json"
      }
    }
  }
}

Environment Variables

| Variable | Required | Default | Description | |----------|----------|---------|-------------| | SLACK_APP_TOKEN | Yes | — | App-level token (xapp-...) with connections:write scope | | PERSIST_PATH | No | — | File path to persist notifications across restarts |

Available MCP Tools

slack_get_notifications

Retrieve stored message notifications with filtering:

  • Filter by channel, read status, time range
  • Pagination support
  • Returns newest messages first

slack_mark_notifications_read

Mark notifications as read:

  • By specific IDs
  • All at once (optionally per-channel)

slack_notification_stats

Get a summary of notification counts grouped by channel — total and unread per channel.

slack_clear_notifications

Permanently delete all stored notifications (requires confirmation).

Building

npm install
npm run build

Running

SLACK_APP_TOKEN=xapp-1-... npm start

The server will connect to Slack via Socket Mode and start the MCP stdio server simultaneously.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Communication servers.