jtalk22/slack-mcp-server

v3.2.4 — Distribution Parity and Support Paths

v3.2.4 restores version parity across the shipped runtime, Docker smoke path, registry metadata, and current public trust surfaces while aligning support paths for self-hosted and managed deployment modes.

npx -y @jtalk22/slack-mcp@latest --version
npx -y @jtalk22/slack-mcp@latest --doctor

Improved

• Runtime version integrity — CLI, setup wizard, HTTP transport, web mode, and Docker smoke output now derive their release version from one canonical metadata source.
• Public trust surfaces — README, landing pages, share/demo pages, and current setup/troubleshooting docs now tell one consistent story: 16 self-hosted tools, 15 managed Cloud tools, and 3 Team AI workflows.
• Release guardrails — CI and release preflight now enforce public-surface integrity and regression-check the Attribution Guardrail Dependabot skip logic.
• Support routing — hosted deployment review and support boundaries are elevated across current repo-facing surfaces so rollout requests and reproducible bugs follow separate paths.

Operations

• Docker publishes on tag push; npm publishes when the GitHub Release object is created. v3.2.4 should be shipped in that order to avoid split-brain distribution.
• External parity is expected to propagate after release. Use node scripts/check-version-parity.js --allow-propagation while npm, MCP Registry, and listing surfaces catch up.
• Current same-day ship steps and monitoring are documented in docs/LAUNCH-OPS.md.

Compatibility

• No MCP tool names were removed or renamed.
• No request/response schemas changed.
• Existing entry points remain intact: --setup, --status, --doctor, web, and http.

Verify

npx -y @jtalk22/slack-mcp@latest --version
npx -y @jtalk22/slack-mcp@latest --doctor
npx -y @jtalk22/slack-mcp@latest --status
docker run --rm ghcr.io/jtalk22/slack-mcp-server:3.2.4 --version

Support

• Cloud deployment review: https://mcp.revasserlabs.com/deployment
• Cloud support: https://mcp.revasserlabs.com/support
• Troubleshooting: https://github.com/jtalk22/slack-mcp-server/blob/main/docs/TROUBLESHOOTING.md
• Support boundaries: https://github.com/jtalk22/slack-mcp-server/blob/main/docs/SUPPORT-BOUNDARIES.md

Maintained by James Lambert (jtalk22) under Revasser.