Slack Archived Reference MCP Server

Your assistant inside the workspace — read channels, search history, post messages and tame the noise.

Local serverstdioTypeScriptMIT★ 63.0k

What is the Slack Archived Reference MCP Server?

This is the archived MCP reference implementation for Slack, hosted in the Model Context Protocol archived-server repository.

Maintenance and ownership

It is a local reference implementation with its own package and credential configuration. The repository is archived. This entry is not the first-party hosted service maintained by Slack, so the official-vendor label is removed from this reference profile.

Prefer the documented current route for a new evaluation

The separate Slack Official profile describes the hosted endpoint, registered-app requirements and supported client path. Use the appropriate publisher instructions for that integration. A local bot-token setup from the archived reference is not interchangeable with a hosted OAuth connection.

When reviewing an older installation

Identify the exact package version, workspace, credential scopes and exposed tools. Inspect whether the deployment still has an active maintenance path before relying on it for a recurring workflow. Start with a known read and verify what data the installed client can reach.

For any messaging workflow, prepare the message and destination before applying a write. Preserve source-thread links in summaries so a reader can separate an actual decision from the assistant’s interpretation. The archived URL remains available to explain existing configurations and historical references.

Publisher documentation

Source 1

What you can do with it

Channel digests

Condense a week of a busy channel into the five things that mattered.

Decision retrieval

Find where something was agreed and quote the actual exchange.

Drafted updates

Compose status updates in context and post them after your approval.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
slack_list_channelsList channels the bot can see
slack_get_channel_historyRead recent messages from a channel
slack_post_messagePost a message to a channel
slack_reply_to_threadReply within a thread
slack_add_reactionReact to a message with an emoji
slack_get_thread_repliesRead a full thread
slack_get_users / slack_get_user_profileLook up workspace members

How to install the Slack Archived Reference MCP Server

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-slack"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-bot-token",
        "SLACK_TEAM_ID": "T01234567"
      }
    }
  }
}

Create a Slack app with bot scopes (channels:read, channels:history, chat:write, reactions:write, users:read), install to workspace, copy the bot token.

Configuration

A Slack app with bot-token scopes installed to your workspace. The bot only sees channels it's invited to.

VariableDescriptionRequired
SLACK_BOT_TOKENBot user OAuth token from your Slack appe.g. xoxb-...Yes
SLACK_TEAM_IDWorkspace/team IDe.g. T01234567Yes
SLACK_CHANNEL_IDSOptional comma-separated channel allowlistOptional

Example prompts to try

  • “Summarise the last week of #incidents — what broke, what's resolved, what's still open?”
  • “Find the thread where we discussed the API rate-limit change and summarise the conclusion.”
  • “Draft a release announcement for #general based on this changelog, then post it.”

Frequently asked questions

The reference server works through a bot token, which sees public channels it's been added to — not your personal DMs. Some community servers support user-token modes with broader visibility; treat those scopes as the sensitive credentials they are.