home / mcp / slack mcp logger server

Slack MCP Logger Server

Provides a Slack-based MCP server for channel management, messaging, and log monitoring across multiple MCP sources.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "caramuto-redhat-slack-mcp-logger": {
      "url": "https://slack-mcp.example.com/sse",
      "headers": {
        "MCP_TRANSPORT": "stdio",
        "LOGS_CHANNEL_ID": "C7000000",
        "SLACK_XOXC_TOKEN": "xoxc-...",
        "SLACK_XOXD_TOKEN": "xoxd-..."
      }
    }
  }
}

You have Slack MCP Server, a dedicated integration that lets your team manage Slack channels, post messages and commands, and monitor logs from multiple MCP sources. It brings Slack-driven collaboration to your log analysis workflow, enabling automated alerts and quick sharing of actionable data with your team.

How to use

Connect your Slack MCP Server to Slack and your log sources, then use a compatible MCP client to send natural language requests. You can ask for recent log data, post alerts to specific channels, and automatically react to important messages to draw team attention. Typical workflows include reading logs from one or more services, analyzing them, and posting summaries or alerts directly into designated Slack channels.

How to install

Prerequisites: install a container runtime (Podman or Docker) and prepare Slack tokens for authentication. You will run the MCP server using containerized commands shown below.

Option A: Run with Podman (as shown in the example configuration) you will start the container with the necessary Slack tokens and transport settings.

{
  "mcpServers": {
    "slack": {
      "command": "podman",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "SLACK_XOXC_TOKEN",
        "-e", "SLACK_XOXD_TOKEN",
        "-e", "MCP_TRANSPORT",
        "-e", "LOGS_CHANNEL_ID",
        "quay.io/redhat-ai-tools/slack-mcp"
      ],
      "env": {
        "SLACK_XOXC_TOKEN": "xoxc-...",
        "SLACK_XOXD_TOKEN": "xoxd-...",
        "MCP_TRANSPORT": "stdio",
        "LOGS_CHANNEL_ID": "C7000000"
      }
    }
  }
}

How to install (continued)

Option B: Run with non-stdio transport when you prefer a push-based or streaming connection. The example below shows how to reach a non-stdio MCP server endpoint using HTTP/SSE transport.

{
  "mcpServers": {
    "slack": {
      "url": "https://slack-mcp.example.com/sse",
      "headers": {
        "X-Slack-Web-Token": "xoxc-...",
        "X-Slack-Cookie-Token": "xoxd-..."
      }
    }
  }
}

Available tools

get_channel_history

Fetch message history for a Slack channel by channel_id.

join_channel

Join a Slack channel, with an option to skip log tracing.

post_message

Post a message to a Slack channel, with optional threading.

post_command

Post a Slack slash-command response to a channel.

add_reaction

Add an emoji reaction to a specific Slack message.

whoami

Identify the authenticated Slack user.

get_server_logs

Read log contents from a specified log file path.