slamy — Slack MCP server & CLI

日本語

A Slack MCP (Model Context Protocol) server that also works as a standalone CLI. Connect AI agents like Claude to your Slack workspace, or use it directly from the terminal.

Features

• MCP Server — expose Slack operations as MCP tools for AI agents (Claude Code, Claude Desktop, etc.)
• CLI — use the same operations directly from the terminal
• Channels — list channels, retrieve message history
• Messages — post messages, reply to threads
• Users — list workspace members, view profiles
• Reactions — add emoji reactions to messages
• Search — search messages across channels with Slack query syntax
• Multiple output formats — human-readable text, JSON, and TSV

Installation

Homebrew

brew install tackeyy/tap/slamy

Go

go install github.com/tackeyy/slamy@latest

Build from source

git clone https://github.com/tackeyy/slamy.git
cd slamy
go build -o slamy .

Quick Start

1. Create a Slack App

1. Go to Slack API and click Create New App
2. Choose From scratch, name your app (e.g., slamy)
3. Select the workspace to install to

2. Configure User Token Scopes

In OAuth & Permissions > Scopes > User Token Scopes, add:

3. Install and Set Environment Variables

Install the app to your workspace, then set your token:

export SLACK_USER_TOKEN=xoxp-your-user-token

4. Run

./slamy channels list

User Token vs Bot Token

Slack Apps can issue two types of tokens. Which one to use depends on your use case.

Use User Token when: acting on behalf of a user

slamy was built as part of an AI secretary / personal assistant (Claude Code + MCP) that reads, searches, and posts to Slack on behalf of a specific user. In this use case, User Token is the natural choice:

1. Search requires it — search:read is a User Token-only scope. Bot Tokens simply cannot search messages
2. Single token — no need to manage two tokens and worry about which operation uses which
3. User context — messages posted by the agent appear as the user, making it clear who is responsible
4. Channel access — the agent can access the same channels as the user without manual invitation

Use Bot Token when: building a bot

Bot Token is the right choice if you are building a Slack bot (not a personal assistant):

• The bot has its own identity and posts as "app name", not as a specific user
• Multiple users interact with the bot — it shouldn't act as any single user
• You want to control access by inviting the bot only to specific channels
• You don't need message search, or can accept the limitation

Commands

channels list — List channels

slamy channels list [--limit <number>] [--include-archived] [--json] [--plain]

channels history — Get channel message history

slamy channels history <channel_id> [--limit <number>] [--json] [--plain]

messages post — Post a message

slamy messages post <channel_id> --text <message> [--json] [--plain]

messages reply — Reply to a thread

slamy messages reply <channel_id> <thread_ts> --text <message> [--broadcast] [--json] [--plain]

users list — List workspace users

slamy users list [--include-deactivated] [--include-bots] [--json] [--plain]

users profile — Get user profile

slamy users profile <user_id> [--json] [--plain]

reactions add — Add emoji reaction

slamy reactions add <channel_id> <timestamp> --name <emoji> [--json] [--plain]

search messages — Search messages

slamy search messages <query> [--count <number>] [--page <number>] [--sort <field>] [--sort-dir <direction>] [--json] [--plain]

auth test — Test authentication

slamy auth test [--json] [--plain]

mcp — Start MCP server

slamy mcp

Starts an MCP server over stdio, exposing all operations as tools for AI agents (e.g., Claude Code).

Configuration

Environment Variables

Output Formats

Text (default)

#general                       C01234ABCDE  [42 members]
#random                        C01234FGHIJ (private)  [15 members]

JSON (--json)

[
  {
    "id": "C01234ABCDE",
    "name": "general",
    "num_members": 42,
    "is_private": false
  }
]

TSV (--plain)

C01234ABCDE	general	42	public
C01234FGHIJ	random	15	private

MCP Server

Usage with Claude Code

claude mcp add slamy /path/to/slamy mcp

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "slamy": {
      "command": "/path/to/slamy",
      "args": ["mcp"],
      "env": {
        "SLACK_USER_TOKEN": "xoxp-your-user-token"
      }
    }
  }
}

Available Tools

Development

# Build
go build -o slamy .

# Run all tests with race detector
go test -race ./...

# Run tests with coverage
go test -cover ./...

See CONTRIBUTING.md for development setup and coding standards. See docs/TESTING.md for the comprehensive testing guide.

Contributing

Contributions are welcome! Please read our Contributing Guide before submitting a Pull Request.

All contributors are expected to follow our Code of Conduct.

License

MIT

Links

• GitHub Repository
• Slack API Documentation
• Model Context Protocol