docs(readme): compare with hosted Slack connector; document cache TTL/refresh envs - #12
Merged
AlexanderMakarov merged 1 commit intoJul 9, 2026
Conversation
…/refresh envs Add a 'Comparison with the hosted Slack connector' section before Tools, covering feature support and how each side caches Slack data. Also bring the docs up to date with recent fork developments: - note has:/hasmy: reaction filters in the Search Messages feature - note rich_text rendering for conversations_add_message payloads - describe TeamID-prefixed, TTL'd, count-merging cache behavior - document the SLACK_MCP_CACHE_TTL and SLACK_MCP_MIN_REFRESH_INTERVAL env vars
📝 WalkthroughWalkthroughREADME.md was updated to expand the Slack MCP Server feature list with search and cache details, replace the hosted connector comparison section with a capability table and caching explanation, and document two new cache-related environment variables. ChangesREADME caching and comparison documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Tools execution failed with the following error: Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error) Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 35: The README privacy statement is too absolute and should be softened
to reflect local control rather than guaranteeing data never leaves the machine.
Update the wording in the project overview so it emphasizes that you run the Go
binary yourself, keep ownership of your tokens and configuration, and control
the self-hosted server, while avoiding any claim that Slack data never leaves
the machine; use the surrounding self-hosted vs hosted Slack connector contrast
to guide the rewrite.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
|
||
| ## Comparison with the hosted Slack connector | ||
|
|
||
| Claude clients (Claude Code, claude.ai, Claude Desktop) can also reach Slack through Anthropic's **hosted Slack connector** — an OAuth Slack app that Anthropic operates on your behalf. This project takes a different route: you run the Go binary yourself with your own tokens (browser-session `xoxc`/`xoxd` "stealth" mode, or `xoxp`/`xoxb`). Nothing has to be installed or approved in your workspace, and your data never leaves the machine the server runs on. |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect the relevant README section with line numbers.
git ls-files README.md
wc -l README.md
sed -n '25,45p' README.md | cat -nRepository: provectus/slack-mcp-server
Length of output: 1975
Tighten the privacy wording here. “Your data never leaves the machine” is too absolute; the self-hosted server still sends Slack data to Slack’s API. Rephrase this as local control/ownership, not data locality.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 35, The README privacy statement is too absolute and
should be softened to reflect local control rather than guaranteeing data never
leaves the machine. Update the wording in the project overview so it emphasizes
that you run the Go binary yourself, keep ownership of your tokens and
configuration, and control the self-hosted server, while avoiding any claim that
Slack data never leaves the machine; use the surrounding self-hosted vs hosted
Slack connector contrast to guide the rewrite.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Comparison with the hosted Slack connector section to the README (placed right before the
## Toolssection), and brings the docs up to date with recent fork developments.New comparison section
xoxc/xoxdstealth, orxoxp/xoxb) vs. a hosted OAuth app.TeamID-prefixed, TTL'd on-disk cache of users/channels for@user/#channelresolution; the connector queries the Slack Web API live with no user-managed cache.Recent-development doc updates (from commit history)
has:/hasmy:reaction filters (feat(search): first-class reaction filters (has:/hasmy:) in conversations_search_messages #9).conversations_add_messagenote now mentions nativerich_textrendering (fix(add_message): render markdown as rich_text, not section blocks #8).SLACK_MCP_CACHE_TTLandSLACK_MCP_MIN_REFRESH_INTERVAL.Why
Docs-only. Makes it clear when to reach for this server vs. the hosted connector, and closes gaps between the code and the README for cache configuration.
Summary by CodeRabbit