@jtalk22/slack-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 4 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p @jtalk22/slack-mcp@5.2.1 slack-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 1 returned a result.
slack_token_status | Returned a result under 0.1 s · 767 characters |
slack_health_check | No usable answer tool reported an error: { "status": "error", "code": "missing_credentials", "message": "No credentials found", "next_action": "Run npx -y @jtalk22/slack |
slack_list_conversations | No usable answer tool reported an error: { "status": "error", "code": "tool_call_failed", "message": "No credentials available. Run npx -y @jtalk22/slack-mcp --setup or op |
slack_list_users | No usable answer tool reported an error: { "status": "error", "code": "tool_call_failed", "message": "No credentials available. Run npx -y @jtalk22/slack-mcp --setup or op |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
slack_token_status
Check token health, age, auto-refresh status, and cache stats
slack_health_check
Check if Slack tokens are valid and show authentication status
slack_refresh_tokens
Force refresh tokens by extracting from Chrome (macOS; requires having signed into Slack in Chrome)
slack_list_conversations types, limit, discover_dms
List all DMs and channels with user names resolved. Uses cached DMs by default for speed.
slack_conversations_history channel_id, limit, oldest, latest, resolve_users, include_rich_message_fields, provenance, include_all_metadata
Get messages from a channel or DM with user names resolved
15 more tools
slack_get_full_conversation channel_id, oldest, latest, max_messages, include_threads, include_rich_message_fields, provenance, include_all_metadata, output_file
Export FULL conversation history with all messages, threads, and user names. Can save to file.
slack_search_messages query, count, include_rich_message_fields, provenance
Search messages across the Slack workspace
slack_users_info user_id
Get detailed information about a Slack user
slack_send_message channel_id, text, thread_ts, provenance, confirm_untrusted_context
Send a message to a channel or DM
slack_get_thread channel_id, thread_ts, include_rich_message_fields, provenance, include_all_metadata
Get all replies in a message thread
slack_list_users limit
List all users in the workspace
slack_add_reaction channel_id, timestamp, reaction
Add an emoji reaction to a message
slack_remove_reaction channel_id, timestamp, reaction
Remove an emoji reaction from a message
slack_conversations_mark channel_id, timestamp
Mark a conversation as read up to a specific message timestamp
slack_conversations_unreads types, limit
Get channels and DMs with unread messages, sorted by unread count (highest first)
slack_users_search query, limit
Search workspace users by name, display name, or email. Case-insensitive partial match.
slack_workflow_save profile_name, workflow_kind, channels, priority_people, retention_mode, summary_cadence
Save or update a workflow profile that binds a workflow_kind (support_inbox | incident_room | exec_brief | product_launch_watch | custom) to channels, priority people, retention mode, and summary cadence. Stored locally at ~/.slack-mcp-workflows.json. slack_catch_me_up reads the profile by name and returns evidence shaped by its workflow_kind.
slack_workflows workflow_kind
List all saved workflow profiles from ~/.slack-mcp-workflows.json. Optionally filter by workflow_kind. Returns profile_name, channels, priority_people, retention_mode, summary_cadence, structured_keys, created_at, updated_at.
slack_catch_me_up profile_name, since
Catch up on a saved workflow profile. Reads the profile's channels (or everything currently unread if the profile names none), pulls messages since the cadence window or an explicit `since`, expands active threads, and returns structured evidence: which threads are unanswered and for how long, what the profile's priority people said or were pinned on, and which conversations moved most. Runs locally against your own session — no hosted account, no server-side model. It also returns a `continuity` block — commitments someone made, asks nobody has claimed, and questions still unanswered — built from phrase and reply-count rules over the same messages, with the matched text and a permalink on every row so each line can be opened and checked. The response carries an `output_contract` naming the keys to compose for this workflow_kind; write the summary from the returned `signals`, `continuity` and `conversations`, citing conversation names and timestamps.
slack_session_report
What this server process has actually done, as counts: how many messages it read, how many of those were written by authors outside this workspace broken down by origin, how many sends were attempted, and how many were held. A provenance label is a claim about one message; this is the claim about the whole session, and it is the only way to check after the fact whether outside-authored text reached the model and whether anything tried to send on the back of it. Counts only — no message text, no channel name, no user id is recorded. The receipt and the strict hold belong to this server process, so over HTTP every client of the process shares them.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20.0.0 |
| Source | github.com/jtalk22/slack-mcp-server |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-zqYwMrKZvwBne9QMO8U+6FMHGFQd3rc2ym4NgqthrTZu//MfoyQ37woq1lNYWjhjGFcXXB7Iz6UITFdHUo56cQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40jtalk22/slack-mcp)
New version out? Ask for a fresh report.