Use this guide to choose the right operating mode before rollout.
stdio for personal use in Claude Desktop/Claude Code.web for browser workflows and manual Slack browsing.| Mode | Start Command | Best For | Auth Material | Exposure | Notes |
|---|---|---|---|---|---|
Local MCP (stdio) |
npx -y @jtalk22/slack-mcp |
Individual daily usage in Claude | SLACK_TOKEN + SLACK_COOKIE via token file/env |
Local process | Lowest ops burden |
Local Web UI (web) |
npx -y @jtalk22/slack-mcp web |
Browser-first usage, manual search/send | Same as above + generated API key | localhost by default |
Useful when MCP is not available |
Hosted MCP (http) |
node src/server-http.js |
Controlled hosted integration | Env-injected Slack token/cookie | Remote endpoint | Requires runtime hardening and monitoring |
| Smithery/Worker | wrangler deploy + Smithery publish flow |
Registry distribution for hosted consumers | Query/env token handoff | Remote endpoint | Keep worker version parity with npm release |
If you are deploying for more than one operator:
stdio./health and MCP initialize responses on every release.stdionpx -y @jtalk22/slack-mcp --statusnpx -y @jtalk22/slack-mcp --helpwebnpx -y @jtalk22/slack-mcp web~/.slack-mcp-api-key./health, /conversations, and /search endpoints.http or Worker)version parity across package.json, server metadata, and health responses.slack_get_thread, slack_search_messages, and slack_users_info behavior.