t1k:comms-mcp:slack
| Field | Value |
|---|---|
| Module | slack |
| Version | 0.5.2 |
| Effort | low |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:comms-mcp:slackSlack (comms-mcp)
Section titled “Slack (comms-mcp)”Read, search, and post Slack messages (channels, threads, DMs) through an MCP server.
Source
Section titled “Source”Wraps The1Studio/slack-mcp-server (fork of korotovsky/slack-mcp-server, MIT). Chosen as the most powerful Slack MCP (~1.9k★ upstream) — supports a no-permission browser-token mode in addition to OAuth, plus DMs, threads, and message search. Ships no published binary/image, so it is built from a fork clone (see Setup).
When to Use
Section titled “When to Use”- Posting notifications/alerts to a Slack channel or DM from an agent
- Reading or searching channel/thread/DM history
- Managing reactions and user groups
- Wiring Slack into a comms workflow
Run ~/.claude/skills/t1k-comms-mcp-setup/scripts/install-slack.sh (for a project-scoped install it’s .claude/skills/t1k-comms-mcp-setup/scripts/install-slack.sh) — clones + builds the fork, then registers the MCP server if a token env var is set, else prints the commands for both auth modes.
Pick exactly one auth credential (priority xoxp > xoxb > xoxc/xoxd):
| Mode | Env | Notes |
|---|---|---|
| User OAuth | SLACK_MCP_XOXP_TOKEN | Most capable — full toolset |
| Bot OAuth | SLACK_MCP_XOXB_TOKEN | Loses search + unreads tools |
| Browser session | SLACK_MCP_XOXC_TOKEN + SLACK_MCP_XOXD_TOKEN | “No-permission” mode; enables saved_* tools. xoxd is a live session cookie — secret; may violate workspace policy/Slack ToS |
- OAuth: api.slack.com/apps → user scopes (
channels:history,im:history,chat:write,search:read,users:read,usergroups:read, …) → install → copyxoxp-…. - Browser: Slack web → DevTools console (type
allow pasting) →JSON.parse(localStorage.localConfig_v2).teams[...].token→xoxc; DevTools → Application → Cookies → cookied→xoxd.
Register (user scope, after build):
claude mcp add slack --scope user --env SLACK_MCP_XOXP_TOKEN=xoxp-... -- /ABS/PATH/slack-mcp-server/build/slack-mcp-server --transport stdioBrowser variant: replace the env flag with --env SLACK_MCP_XOXC_TOKEN=... --env SLACK_MCP_XOXD_TOKEN=....
Prereqs: Go 1.25 (GOTOOLCHAIN=local); one valid auth credential; built build/slack-mcp-server.
Write tools are OFF by default — set SLACK_MCP_ADD_MESSAGE_TOOL (enables conversations_add_message), SLACK_MCP_REACTION_TOOL, SLACK_MCP_ATTACHMENT_TOOL, or list in SLACK_MCP_ENABLED_TOOLS.
MCP Tools (22)
Section titled “MCP Tools (22)”| Group | Tools |
|---|---|
| Read | conversations_history, conversations_replies, conversations_search_messages¹, conversations_unreads¹, channels_list, channels_me, users_search, usergroups_list, usergroups_me |
| Write (gated) | conversations_add_message², reactions_add³, reactions_remove³, attachment_get_data⁴ |
| Manage | conversations_mark, conversations_join, conversations_leave, usergroups_create, usergroups_update, usergroups_users_update |
| Browser-only | saved_list, saved_update, saved_clear_completed (xoxc/xoxd only) |
¹ not available on bot (xoxb) tokens · ² needs SLACK_MCP_ADD_MESSAGE_TOOL · ³ needs SLACK_MCP_REACTION_TOOL · ⁴ needs SLACK_MCP_ATTACHMENT_TOOL.
Resources: slack://<ws>/channels, slack://<ws>/users.
Hard rules
Section titled “Hard rules”- Browser-token mode —
xoxdis a live session cookie; treat as secret and note it may violate workspace policy/Slack ToS.