Skip to main content
Glama

mcp-slack

MCP server for Slack integration, built with FastMCP. Provides tools for listing channels, reading messages, and posting to Slack.

Channel listing and reading are observational. slack_post_message performs an external write immediately when invoked, so callers should confirm the resolved destination and message content before calling it.

Install

pip install -e ".[dev]"

Related MCP server: slack-mcp-server

Environment Variables

Variable

Required

Description

SLACK_BOT_TOKEN

Yes

Bot User OAuth Token (xoxb-...)

SLACK_DEFAULT_CHANNEL

No

Current fallback channel when slack_post_message receives an empty channel

Copy .env.example to .env and fill in your values.

Tools

Tool

Description

slack_list_channels

List all channels accessible by the bot

slack_read_channel(channel, limit?)

Read last N messages from a channel (default: 20, max: 100)

slack_post_message(channel, text)

Send a message to a channel

The channel parameter accepts a channel name (without #) or a public-channel ID beginning with C. Correct handling for other Slack conversation ID types is tracked in Issue #8.

Slack App Setup

  1. Go to api.slack.com/apps and create a new app

  2. Under OAuth & Permissions, add the required Bot Token Scopes for the tools you want to use:

    Tool

    Required Bot Scopes

    slack_list_channels

    channels:read, groups:read

    slack_read_channel

    channels:history, groups:history

    slack_post_message

    chat:write

    Note: Private-channel access requires the corresponding groups:* scopes and bot membership. Direct-message and multi-party conversation support is not currently implemented; the supported conversation contract is tracked in Issue #8.

  3. Install the app to your workspace

  4. Copy the Bot User OAuth Token (xoxb-...) to SLACK_BOT_TOKEN

  5. Invite the bot to channels it should access: /invite @your-bot-name

Troubleshooting: missing_scope Error

If a tool fails with a missing_scope error, it means the bot doesn't have the necessary permissions to perform that action. Check the error message to see which scope is missing, cross-reference it with the table above, and add the missing scope in your Slack App's OAuth & Permissions page. (Remember to reinstall the app to your workspace after changing scopes!)

Usage

Standalone

mcp-slack

Claude Desktop config

{
  "mcpServers": {
    "slack": {
      "command": "mcp-slack",
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token"
      }
    }
  }
}

Development

pip install -e ".[dev]"
ruff check src/ tests/
ruff format src/ tests/
pytest

License

MIT

Documentation and roadmap

Priorities live in GitHub Issues and Projects. Delivery history lives in closed Issues, pull requests and GitHub Releases.

Available Tools

3 tools
slack_list_channelsA

List all Slack channels accessible by the bot.

Returns a formatted list of channel names with their IDs and topics.

Inputs: no named parameters. Returns: result

slack_post_messageA

Send a message to a Slack channel.

Args: channel: Channel name (without #) or channel ID. text: The message text to send. Supports Slack markdown.

Inputs: text (required), channel (required). Returns: result

slack_read_channelA

Read the last N messages from a Slack channel.

Args: channel: Channel name (without #) or channel ID. limit: Number of messages to retrieve (default: 20, max: 100).

Inputs: channel (required), limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct Slack action+resource: listing channels, reading messages, and posting messages. There is no overlap in purpose or argument shape between them.

    Naming Consistency5/5

    All three tools use a consistent slack_ prefix with a clear verb_noun pattern (slack_list_channels, slack_read_channel, slack_post_message). The convention is predictable throughout.

    Tool Count3/5

    Three tools is on the thin side for a Slack integration; the set covers only the most basic read/write loop. It is functional but leaves little room for common adjacent operations.

    Completeness3/5

    Core operations (list channels, read messages, post message) are present, but there are notable gaps: no thread replies, reactions, message search, user/DM lookup, or message editing. Agents can do basic workflows but will hit dead ends on common Slack tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers