Slack MCP Server
NPM · @JTALK22/SLACK-MCP · 2 COMPONENTS · SCANNED SEP 20
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 23 of 74 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jtalk22/slack-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1714 tokens (~81/item across 21 items; 19 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Slack MCP Server server?
Slack MCP Server runs locally as an npm package, launched with npx -y @jtalk22/slack-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @jtalk22/slack-mcp
claude mcp add jtalk22-slack-mcp-server -- npx -y @jtalk22/slack-mcp
{
"mcpServers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
} {
"servers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
} codex mcp add jtalk22-slack-mcp-server -- npx -y @jtalk22/slack-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jtalk22-slack-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@jtalk22/slack-mcp"
],
"enabled": true
}
}
} openclaw mcp add jtalk22-slack-mcp-server --command npx --arg -y --arg @jtalk22/slack-mcp
mcp_servers:
jtalk22-slack-mcp-server:
command: "npx"
args: ["-y", "@jtalk22/slack-mcp"] {
"McpServers": {
"jtalk22-slack-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
} assistant mcp add jtalk22-slack-mcp-server -t stdio -c npx -a -y @jtalk22/slack-mcp
{
"mcpServers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Stability: fail → 0.90 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 84 to 87.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 13 Sept 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 90 to 70.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 84 to 87.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 8 Sept 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 90 to 77.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 84 to 87.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@jtalk22/slack-mcp@5.0.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jtalk22/slack-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jtalk22/slack-mcp-server/.github/workflows/publish.yml@refs/tags/v5.0.0 |
| Rekor log index | 2582102811 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ac0c227f1a79c8e9c2a9a51ff6d13ca83bf4f26028cdd0592c459444ca352e434d3d9abc925df861639f0842a8363676dda6eebcfc40be8dbe24e031d |
Background: How many MCP packages publish verified provenance →
Dependencies 74 packages
| Packages resolved | 74 |
|---|---|
| Stale | 23 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
slack_add_reaction ~72
Add an emoji reaction to a message
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID containing the message |
| reaction | string | yes | Emoji name without colons (e.g., 'thumbsup', 'eyes', 'white_check_mark') |
| timestamp | string | yes | Message timestamp to react to |
No output schema declared.
No examples provided.
slack_catch_me_up ~212
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. The response carries an `output_contract` naming the keys to compose for this workflow_kind; write the summary from the returned `signals` and `conversations`, citing conversation names and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_name | string | yes | Name of a workflow profile saved via slack_workflow_save (list them with slack_workflows) |
| since | string | – | Optional ISO 8601 timestamp — only consider messages newer than this. Defaults to the profile's cadence window: 24 hours for on_demand and daily_8am, 7 days for weekly_monday. |
No output schema declared.
No examples provided.
slack_conversations_history ~161
Get messages from a channel or DM with user names resolved
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID (e.g., D063M4403MW) |
| include_all_metadata | boolean | – | Pass Slack's include_all_metadata option to conversations.history |
| include_rich_message_fields | boolean | – | Include Slack message attachments, blocks, metadata, files, and reactions when present |
| latest | string | – | Unix timestamp - get messages before this time (boundary timestamp included) |
| limit | number | – | Messages to fetch (max 100, default 50) |
| oldest | string | – | Unix timestamp - get messages after this time (boundary timestamp included) |
| resolve_users | boolean | – | Convert user IDs to names (default true) |
No output schema declared.
No examples provided.
slack_conversations_mark ~63
Mark a conversation as read up to a specific message timestamp
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID to mark as read |
| timestamp | string | yes | Message timestamp to mark as read up to (all messages at or before this are marked read) |
No output schema declared.
No examples provided.
slack_conversations_unreads ~68
Get channels and DMs with unread messages, sorted by unread count (highest first)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum conversations to return (default 50) |
| types | string | – | Comma-separated types: im, mpim, public_channel, private_channel (default all) |
No output schema declared.
No examples provided.
slack_get_full_conversation ~194
Export FULL conversation history with all messages, threads, and user names. Can save to file.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID |
| include_all_metadata | boolean | – | Pass Slack's include_all_metadata option to conversations.history and conversations.replies |
| include_rich_message_fields | boolean | – | Include Slack message attachments, blocks, metadata, files, and reactions when present |
| include_threads | boolean | – | Fetch thread replies (default true) |
| latest | string | – | Unix timestamp end (boundary timestamp included) |
| max_messages | number | – | Maximum messages to retrieve (default 2000, max 10000) |
| oldest | string | – | Unix timestamp start (e.g., 1733011200 = Dec 1, 2025; boundary timestamp included) |
| output_file | string | – | Filename to save export (saved to ~/.slack-mcp-exports/) |
No output schema declared.
No examples provided.
slack_get_thread ~87
Get all replies in a message thread
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID |
| include_all_metadata | boolean | – | Pass Slack's include_all_metadata option to conversations.replies |
| include_rich_message_fields | boolean | – | Include Slack message attachments, blocks, metadata, files, and reactions when present |
| thread_ts | string | yes | Thread parent message timestamp |
No output schema declared.
No examples provided.
slack_health_check ~20
Check if Slack tokens are valid and show authentication status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slack_list_conversations ~101
List all DMs and channels with user names resolved. Uses cached DMs by default for speed.
| Name | Type | Req | Description |
|---|---|---|---|
| discover_dms | boolean | – | If true, actively discover all DMs (slower, may hit rate limits on large workspaces). Default false uses cached DMs. |
| limit | number | – | Maximum results (default 100) |
| types | string | – | Comma-separated types: im, mpim, public_channel, private_channel |
No output schema declared.
No examples provided.
slack_list_users ~34
List all users in the workspace
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum users to return (default 500, supports pagination) |
No output schema declared.
No examples provided.
slack_refresh_tokens ~24
Force refresh tokens by extracting from Chrome (requires Slack tab open in Chrome)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slack_remove_reaction ~68
Remove an emoji reaction from a message
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID containing the message |
| reaction | string | yes | Emoji name without colons (e.g., 'thumbsup', 'eyes') |
| timestamp | string | yes | Message timestamp to remove reaction from |
No output schema declared.
No examples provided.
slack_search_messages ~81
Search messages across the Slack workspace
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of results (max 100, default 20) |
| include_rich_message_fields | boolean | – | Include Slack message attachments, blocks, metadata, files, and reactions when present |
| query | string | yes | Search query (supports Slack syntax like from:@user, in:#channel) |
No output schema declared.
No examples provided.
slack_send_message ~61
Send a message to a channel or DM
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Channel or DM ID to send to |
| text | string | yes | Message text (supports Slack markdown) |
| thread_ts | string | – | Thread timestamp to reply to (optional) |
No output schema declared.
No examples provided.
slack_token_status ~23
Check token health, age, auto-refresh status, and cache stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
slack_users_info ~28
Get detailed information about a Slack user
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Slack user ID |
No output schema declared.
No examples provided.
slack_users_search ~64
Search workspace users by name, display name, or email. Case-insensitive partial match.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return (default 20) |
| query | string | yes | Search term to match against name, display name, real name, or email |
No output schema declared.
No examples provided.
slack_workflow_save ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | Slack channel IDs to read (e.g. ['C012345', 'C067890']) |
| priority_people | array | – | Slack user IDs whose messages get extra weight in summaries |
| profile_name | string | yes | Unique name for this workflow profile (e.g. 'morning-exec-brief', 'on-call-rotation') |
| retention_mode | string | – | Retention preference recorded on the profile. Default ephemeral. |
| summary_cadence | string | – | How often this profile expects to be caught up on. Sets slack_catch_me_up's default window: 24 hours for on_demand and daily_8am, 7 days for weekly_monday. |
| workflow_kind | string | yes | Workflow kind. Determines the output_contract keys slack_catch_me_up returns for this profile. |
No output schema declared.
No examples provided.
slack_workflows ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_kind | string | – | Optional filter — return only profiles of this workflow_kind |
No output schema declared.
No examples provided.
What is the Slack MCP Server server?
Slack MCP Server is listed in the public MCP registry as io.github.jtalk22/slack-mcp-server. Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. This page covers its npm package (@jtalk22/slack-mcp).
Is the Slack MCP Server server safe to use?
Slack MCP Server scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Slack MCP Server server expose?
Slack MCP Server exposes 19 tools: slack_token_status, slack_health_check, slack_refresh_tokens, slack_list_conversations, slack_conversations_history, and 14 more. Their descriptions and schemas cost roughly 1,687 tokens of context every time the server is loaded.
Is the Slack MCP Server server still maintained?
Slack MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Slack MCP Server server under?
Slack MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.