Browser-session engine
Chrome LevelDB, cookie SQLite + WAL, macOS Keychain, PBKDF2, and AES decryption—locally, with structured failure codes.
Catch up on Slack without reading it
Ask what happened.
Get receipts.
Close the loop.
Turn Slack from an interruption stream into searchable operating memory and approved action. Run the 21-tool surface available today locally with no app/admin queue, or move recurring work to hosted permanent OAuth, indexing, and schedules.
npx -y @jtalk22/slack-mcp --setup
Claude Code · Claude Desktop · Cursor · Copilot · Windsurf · Gemini CLI · Codex CLI · any stdio MCP client
Monday, 9:07. Slack has already formed opinions.
47 → 1 → 0 AFTER APPROVAL
01 / OUTCOME
What blew up overnight?
Slack noise goes in. A prioritized operating brief comes out.
The agent inventories unread channels and DMs, retrieves the history that matters, finds buried details, and closes approved loops through real Slack tool calls.
47
unread messages competing for attention
4
conversations with work that actually matters
1
prioritized brief with owners, risks, and next actions
0
Slack tabs required to understand the morning
02 / SYSTEMS
Built past the demo.
The difficult part is not another chat tool. It is the operating layer underneath.
The local path combines browser-session extraction, a real credential lifecycle, full-fidelity Slack reads, guarded action tools, and automation-ready output.
Credential lifecycle
Keychain-only storage, owner-only files, atomic writes, cross-process locks, health monitoring, refresh, and isolated workspace profiles.
Full-fidelity reads
DMs, channels, search, complete histories, threads, unread state, users, blocks, attachments, files, reactions, and metadata.
Approved action
Replies, reactions, and read-state changes with MCP destructive annotations so the client can gate workspace writes.
Typed workflows
Incident, executive, support, launch, and custom profiles that turn Slack into contract-shaped JSON rather than prompt-shaped glue.
03 / ACCESS
Same workspace. Different gate.
Slack already knows who you are.
The official path is a managed remote integration governed by workspace policy. The local path starts from the browser session you already have; the hosted path turns the same operating jobs into durable, unattended workflows.
Move now.
One-command setup, existing browser permissions, the full current tool surface, and the runtime on your machine. Best for interactive, operator-driven work.
Run local setup →Run unattended.
Indexed retrieval, AI triage, scheduled briefs, shared profiles, managed workspaces, and no browser-session rotation.
See hosted →If you can read it in Slack, your agent can work from it.
Make Slack useful.
Without living in it.
npx -y @jtalk22/slack-mcp --setup