slack-to-laptop
Provides tools for interacting with Slack's API, enabling AI agents to listen to @mentions, send messages, and manage streamed thread responses in Slack channels.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
slack-to-laptop
One long-lived local process, three hats: Slack @mention listener (Socket Mode),
remote HTTP MCP server that Claude Code worktree jobs call to drive the native
Slack stream, and SwiftBar menubar status.
threadTs is the correlation key: the worktree job only ever knows threadTs;
this process maps it to the real Slack stream id. The map is snapshotted to
~/.cache/slack-to-laptop/registry.json, so restarting the bridge (deploys,
crashes) doesn't interrupt running jobs: on boot, restored streams are
force-rotated by the first keepalive tick — rotation doubles as recovery.
How it's built / build your own: RECIPE.md.
Slack app (one-time)
https://api.slack.com/apps → Create New App → From scratch.
Agents & AI Apps feature → toggle ON (grants
assistant:write, required for streams + setStatus).Socket Mode → ON → create app-level token with scope
connections:write→ that'sappToken(xapp-…).OAuth & Permissions → bot scopes:
app_mentions:read,chat:write,assistant:write.Event Subscriptions → subscribe to bot event
app_mention.Install to workspace →
botToken(xoxb-…). Invite the bot to your channel:/invite @YourApp.
Note: Slack docs say setStatus is migrating from assistant:write to chat:write — both scopes above cover either.
Related MCP server: Slack Note Capture MCP Server
Run
mkdir -p ~/.config/slack-trigger
cp config.example.json ~/.config/slack-trigger/config.json
# fill botToken + appToken
bun run server.tsallowedUserIds (Slack user IDs): when non-empty, only those users can trigger
jobs — anyone else gets a threaded "only can trigger me" reply. Empty =
anyone in the channel.
With jobCommand: null, mentioning the bot runs a smoke demo: instant thinking
checklist, two task cards ticking, "hi", stream closed. That validates the whole
Slack side before wiring any jobs.
Wire real jobs
Set jobCommand in the config — a zsh command run per mention with env:
var | value |
| correlation token — pass to every MCP tool call |
| channel id |
| mention text, bot mention stripped |
| unique per mention — use for the worktree name |
|
|
Example: "jobCommand": "/Users/you/projects/slack-to-laptop/scripts/launch-job.zsh" —
see scripts/launch-job.zsh (machine-specific: herdr + repo hardcoded).
It spawns a worktree Claude with prompt /slack-ta [threadTs:$SLACK_THREAD_TS] $SLACK_PROMPT:
the token travels inside the prompt, since the job's Claude only sees what the
skill receives (see "Job-side skill" below).
Connect the worktree's Claude to the MCP (once, user scope):
claude mcp add --transport http --scope user slack-stream http://127.0.0.1:8365/mcpMCP tools
All take threadTs (from SLACK_THREAD_TS):
register_job({threadTs, cwd, paneId?, pid?, branch?})— call once at boot; where the session lives, for follow-up routing (paneId=$HERDR_PANE_ID, or$TMUX_PANEon the tmux fallback)thinking_step({threadTs, title, status, id?, details?})— checklist step;status ∈ pending|in_progress|complete|error; sameid/title updates the stepappend_text({threadTs, markdown})— prose in the progress message (important mid-course findings only)set_status({threadTs, text})— grey "is …" line;""clearsfinish({threadTs, markdown?})— settle the progress message + postmarkdownas its own final-report reply (the user's one notification). Call exactly once, last (again after each follow-up).
Follow-ups
Mentioning the bot again in a job's thread does NOT spawn a second job: the
bridge looks the thread up in ~/.cache/slack-to-laptop/jobs.json (written by
register_job, survives finish for 7 days), verifies the session's pane
still sits in the job's worktree (a pane id alone is not a handle — tmux
recycles them, herdr re-issues them on pane move — so cwd is ground truth),
and types [slack follow-up threadTs:…] <text> into that Claude session —
mid-work it's a steering message, after finish a new turn with full context. A
stream is reopened first if needed ("Reconnecting to session…"). If the pane is
gone, it falls back to spawning a fresh job with a note. Only the typing is
multiplexer-specific (src/inject.ts); finding the session is
registration-based and generic.
Multiplexers (herdr + tmux)
Jobs run under herdr; tmux is still read for follow-up routing, so sessions started before the migration stay reachable.
Launching (
scripts/launch-job.zsh) is herdr-only. It setsHERDR_ENV=1and runswt spawndirectly — no throwaway window. The tmux version needed one because the monorepo'ssetup-tmuxhook exits silently without$TMUX; herdr's layout drives the herdr server over its socket, so nothing has to run inside a pane. If no server is up (fresh boot) it starts one headless, the counterpart oftmux new-session -d.Follow-ups (
src/inject.ts) list both multiplexers and merge the panes; a dead one can't hide the other's. Each pane carries itsmux, and the injection dispatches on it:herdr pane send-text+ anenterkey, ortmux send-keys -l+Enter.herdr labels the recognised agent outright (
"agent": "claude"), so no command-name guessing is needed on that side; the tmux heuristic (the claude CLI shows up as its version number) still covers tmux panes.
Measured herdr gotchas: see RECIPE.md.
A job that dies without finish gets swept: streams idle > staleStreamMinutes are stopped and cleared.
Why each job gets ONE progress message (stream, then chat.update edits after
~3.5 min) and the Slack API quirks behind it: see RECIPE.md.
Job-side skill
Don't make each job improvise the streaming protocol — give your agent a skill
(e.g. ~/.claude/skills/slack-ta/) that owns it. The launch command passes the
correlation token inside the prompt (/slack-ta [threadTs:…] <task>); the skill
should: extract threadTs and pass it to every slack-stream MCP call, open a
thinking_step immediately, update the checklist at real milestones only,
append_text for the final summary, and ALWAYS finish — also on failure. Two
error rules worth copying: if the token is missing, do the work but skip
streaming; if a call errors with "no live stream", the stream was swept —
continue the work, stop streaming.
GET /healthz lists active streams.
How it's built
Architecture, build-your-own steps, and the measured Slack/herdr/SwiftBar gotchas (5-min stream kill, edit-in-place conversion, block quirks, pane verification…) live in RECIPE.md.
SwiftBar
cp swiftbar/slack-to-laptop.sh ~/Library/Application\ Support/SwiftBar/Plugins/ # or your plugin dir
chmod +x .../slack-to-laptop.shStreamable plugin: SwiftBar owns the process lifecycle; menubar shows 🛰️ + active
stream count. Don't also run bun run server.ts manually (port collision).
Test from a terminal first: ./swiftbar/slack-to-laptop.sh — you should see
blocks starting with ~~~. Logs: ~/.cache/slack-to-laptop/server.log
(written by the server itself — NEVER add a stderr redirect to the plugin
script: closing SwiftBar's stderr pipe makes it spin at 100%+ CPU).
SwiftBar does NOT respawn the process if it dies. To restart the bridge:
open -g "swiftbar://refreshplugin?name=slack-to-laptop" (or SwiftBar menu →
plugin → Refresh). If the 🛰️ icon is missing but the process runs, check
defaults read com.ameba.SwiftBar for "NSStatusItem VisibleCC slack-to-laptop.sh" = 0 and write it back to -bool true.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted Slack MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Related MCP Servers
- -licenseNot gradedqualityBmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm91,952MIT
- FlicenseAqualityNot gradedmaintenanceEnables two-way communication between Claude and Slack for posting messages, managing threads, and handling files. It specifically supports asynchronous workflows by allowing Claude to poll for remote user replies and send task notifications.9-
- AlicenseAqualityDmaintenanceMCP server that connects Claude Code to Slack, allowing two-way communication via Slack Socket Mode without tunnels.1MIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT