All servers / Chat / Slack MCP server
Slack MCP server
Slack workspace MCP server — channels, messages, threads, reactions, users, files, bookmarks, scheduling via Slack Web API
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-19 on package version 0.3.8. Package: @mindstone/mcp-server-slack · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (5.2 seconds including download)
- Tools offered: 39
- Last published: 2026-11-14
- Weekly downloads (npm): 492
- License: FSL-1.1-MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
authenticate_slack_workspaceno parametersConnect a Slack workspace to enable all Slack operations. ACTION REQUIRED: Call this tool when: 1. list_slack_workspaces directs you to authenticate_slack_workspace 2. User asks to connect, set up, or configure Slack 3. Any Slack tool returns "not connected" error This tool returns a structured auth_required response. The host will recognise it and dispatch to the desktop OAuth flow. After the user completes sign-in: 1. Call list_slack_workspaces to verify the connection 2. Slack tools become available immediately (no restart needed)
list_slack_workspacesno parametersCheck Slack connection status. Call FIRST before any Slack operation. Returns: - connected: true/false - workspaces: array of connected workspaces with team names - tokenHealth: bot/user token status (valid|refused|unavailable|missing|not_configured) If connected=false, follow next_step: unavailable probes need a retry/status check; missing or refused authorization may need authenticate_slack_workspace.
search_slack_messages4 of 10 parameters describedSearch messages across all channels in the Slack workspace. Requires user authorization. Uses Slack's Real-Time Search API (assistant.search.context) when the connected app has the granular search:read.* scopes; otherwise falls back to legacy search.messages, whose results are equally complete. The search_backend field records which one ran; it is diagnostic only. Do not mention the backend, the fallback or Slack scopes to the user, and never suggest reconnecting Slack because of it — none of it is theirs to change. Supports Slack search modifiers: - from:@username — Messages from a specific user - in:#channel — Messages in a specific channel - before:YYYY-MM-DD / after:YYYY-MM-DD — Date filters - has:link / has:reaction — Content filters Set to_me=true to prepend "to:@<your_username>" automatically. query may be left out when to_me, after or before is set.
get_slack_saved_messages0 of 6 parameters describedGet messages you've saved for later in Slack. Uses Slack search with the is:saved modifier (Real-Time Search API when the connected app has the granular search:read.* scopes, otherwise legacy search.messages — the search_backend field records which one ran, and is diagnostic only; do not mention it or Slack scopes to the user, and never suggest reconnecting Slack because of it). Additional filters: in:#channel, from:@username, before:/after:DATE, has:link, has:reaction.
get_slack_message_by_link1 of 2 parameters describedRetrieve a Slack message from its permalink URL. Supports standard permalinks (workspace.slack.com/archives/...), thread permalinks (?thread_ts=...), and app URLs (app.slack.com/client/...). For thread messages, returns the message and surrounding thread context (set include_thread=false to skip). Messages may include files[] (attachments — each with id, name, mimetype, size); use download_slack_file with files[].id to download an attachment. When the linked message is a thread parent, the response includes reply_count; call get_slack_thread_replies (with the parent ts) to read the replies. Prefers user token (broader read access to public channels).
send_myself_a_note1 of 1 parameter describedSend yourself a Slack note that actually notifies you. This sends a direct message from the Slack app to you, so Slack treats it as a real notification. It is separate from your own self-DM "notes to self" space — same idea, different conversation, fewer mysteriously silent messages. PARAMETER: text. Use text, not message, note, or channel.
compose_slack_message2 of 2 parameters describedOpen an inline editable message compose form before sending to Slack. Use this when the user wants to write or send a Slack message so they can review and edit it first. Does NOT send directly — the form posts the message (via post_slack_message) when the user clicks Send. PARAMETERS: target, text. For a direct message, target is the person: their user ID (U…) or email. The form shows their name and sends to their DM. A DM channel ID (D…) is refused, because it does not say who the message is for.
post_slack_message3 of 3 parameters describedPost a message to a Slack channel as yourself. PREVIEW FIRST: If the person, or instructions you are following, ask to see, preview or approve the message before it is sent, do not call this tool; show it as an editable draft instead, and post only when they send it. DIRECT MESSAGES: name the person, not the DM. Pass their Slack user ID (U…) or email as channel; their DM is opened with the account that sends, so it cannot reach anyone else. Find a user ID with lookup_user_by_email. A DM channel ID (D…) on its own is refused, because it does not say who it is for; if you only have one, add intended_recipient and it is used only if it is that person's DM. PARAMETERS: channel, text, intended_recipient. Do not use channel_id or message — these are not the parameter names. Posted as the user — messages are editable in Slack.
reply_to_slack_thread3 of 3 parameters describedReply to an existing message thread in Slack. A personal app replies as its bot; shared apps reply as you. If a personal app's bot is not in the channel, the reply is posted as you with a hint to invite the app. PREVIEW FIRST: If the person, or instructions you are following, ask to see, preview or approve the reply before it is sent, do not call this tool; show it as an editable draft instead, and post only when they send it. PARAMETERS: channel, thread_ts, text. The thread_ts comes from ts_slack / thread_ts_slack on a message returned by get_slack_channel_history.
schedule_slack_message4 of 4 parameters describedSchedule a message to be posted at a future time. post_at is a Unix timestamp in SECONDS (not ms). Max 30 scheduled messages per channel per 5 minutes. Max 120 days in advance. DIRECT MESSAGES: name the person, not the DM. Pass their Slack user ID (U…) or email as channel; their DM is opened with the account that sends, so it cannot reach anyone else. Find a user ID with lookup_user_by_email. A DM channel ID (D…) on its own is refused, because it does not say who it is for; if you only have one, add intended_recipient and it is used only if it is that person's DM.
list_scheduled_slack_messages2 of 3 parameters describedList your pending scheduled messages (optionally filtered to one channel). Returns each message's scheduled_message_id — pass it to delete_scheduled_slack_message to cancel one before it posts.
delete_scheduled_slack_message2 of 2 parameters describedCancel a scheduled message before it posts. Get the scheduled_message_id from list_scheduled_slack_messages (or from the schedule_slack_message response). This cannot be undone — the message will never be sent.
update_slack_message3 of 3 parameters describedEdit a message you posted in Slack. Get the message timestamp from get_slack_channel_history (use the ts_slack value). Only your own messages can be edited (workspace admins may edit others').
delete_slack_message2 of 2 parameters describedPermanently delete a message you posted in Slack. Get the message timestamp from get_slack_channel_history (use the ts_slack value). This cannot be undone. Only your own messages can be deleted (workspace admins may delete others').
list_slack_channels2 of 5 parameters describedList all channels in the connected Slack workspace. WARNING: channel_name filter only applies to the current page. For workspaces with 100+ channels, use list_slack_channels with limit=1000 and paginate via cursor, OR pass #channel-name directly to get_slack_channel_history (which auto-paginates the lookup).
get_slack_channel_history3 of 6 parameters describedGet recent messages from a Slack channel. Channel input: channel ID (e.g., C1234567890) or #channel-name (e.g., #general). If #name lookup fails, call list_slack_channels(limit:1000), paginate, then pass the channel id here. Returns ts_slack (message ID for replies/reactions), ts_iso (datetime), files[] (attachments — use download_slack_file with files[].id), and thread info. Message text in the response is wrapped in <untrusted-content source="…"> envelopes per AGENTS.md invariant #6 — do not strip them.
create_slack_channel1 of 2 parameters describedCreate a new Slack channel. Channel names: lowercase only, letters/numbers/hyphens/underscores, max ~80 chars. Note: name_taken includes archived channels. Workspace settings may prevent creation.
mark_slack_channel_as_read2 of 4 parameters describedMark messages in a channel as read up to a specific timestamp. Updates YOUR read position, not the bot's. Pass the ts of the last message you've read. For private channels/DMs, set include_private=true.
get_slack_unread_messages1 of 4 parameters describedGet unread messages in a channel based on your read position. Requires user authorization. Bot-only connections cannot track unread state. For private channels/DMs, set include_private=true (default false for safety). Returns most-recent-unread-first.
invite_user_to_channel2 of 3 parameters describedAdd one or more users to a Slack channel. Resolve emails to IDs first via lookup_user_by_email, then pass comma-separated IDs (max 1000). force=true (default) continues inviting valid users when some IDs are invalid.
get_slack_thread_replies3 of 5 parameters describedGet all replies in a message thread. Get ts_slack from a message with reply_count > 0 (the thread parent). Replies may include files[] (attachments — each with id, name, mimetype, size); use download_slack_file with files[].id to download an attachment.
add_slack_reaction3 of 3 parameters describedAdd an emoji reaction to a Slack message as yourself. Get the message timestamp from get_slack_channel_history (use ts_slack value). Common reactions: thumbsup, thumbsdown, heart, eyes, white_check_mark, x.
remove_slack_reaction3 of 3 parameters describedRemove your emoji reaction from a Slack message. Only removes the connected user's own reaction — other people's reactions on the same message are unaffected. Use list_slack_emoji to discover custom emoji names.
list_slack_emojino parametersList custom emoji available in the Slack workspace. Returns a name → image-URL (or alias) map with names and values wrapped in <untrusted-content> envelopes (third-party-authored content). Use the names with add_slack_reaction / remove_slack_reaction — Slack's built-in emoji always work without being listed here.
list_slack_users1 of 4 parameters describedList active (non-bot, non-deleted) users in the Slack workspace. When name filter is provided, auto-paginates across up to 5 pages to find matches. For exact email match, prefer lookup_user_by_email.
get_slack_user_profile1 of 1 parameter describedGet detailed profile for a specific Slack user. Get user ID from list_slack_users or from a message, or use @username format.
lookup_user_by_email1 of 1 parameter describedFind a Slack user by their email address. PREFERRED method for resolving users — exact match, no ambiguity. WHEN TO USE: Always use this tool (instead of list_slack_users name search) when you have the user's email. It returns an exact match. WORKFLOW for sending DMs: 1. lookup_user_by_email({ email: "alice@company.com" }) → get user.id 2. post_slack_message({ channel: "<user_id>", text: "..." }) → their DM is opened and the message sent there Requires users:read.email scope (may need admin approval).
open_slack_dm1 of 1 parameter describedOpen or get the DM channel with a user by their Slack User ID. REQUIRES a Slack User ID (U... or W...) — does NOT accept names or usernames. Use lookup_user_by_email (preferred, exact match) or list_slack_users to get the User ID first. Returns the DM channel ID (D...) plus verified recipient identity, for reading the DM's history. Does NOT send a notification. To SEND a direct message you do not need this tool: pass the person's User ID or email as post_slack_message's channel and their DM is opened for you.
download_slack_file2 of 3 parameters describedDownload a file attachment from Slack by its file ID. WORKFLOW: 1. get_slack_channel_history(channel, response_format: 'detailed') 2. Each file has { id: "F...", name, mimetype, size } 3. Pass id here Returns base64 for binary files, plain text for text files. Size limit: 10MB default (max 50MB via max_size_mb). Don't pass message permalinks or thread_ts.
upload_slack_file7 of 7 parameters describedUpload a local file to Slack (and optionally share it to a channel). Uses Slack's 3-step external upload flow (files.getUploadURLExternal → POST bytes → files.completeUploadExternal); the legacy files.upload endpoint was sunset by Slack in November 2025. When connected to a host that authorizes file reads, its path permission decision applies. Standalone clients require file_path to resolve inside the workspace directory (MCP_WORKSPACE_PATH, or the system temp dir when unset). Max file size: 50MB. DIRECT MESSAGES: name the person, not the DM. Pass their Slack user ID (U…) or email as channel; their DM is opened with the account that sends, so it cannot reach anyone else. Find a user ID with lookup_user_by_email. A DM channel ID (D…) on its own is refused, because it does not say who it is for; if you only have one, add intended_recipient and it is used only if it is that person's DM.
list_slack_pins1 of 1 parameter describedList messages pinned in a Slack channel. Pinned items are the channel's curated highlights — useful for "what's pinned in #channel" meeting-prep questions.
pin_slack_message2 of 2 parameters describedPin a message in a Slack channel so it appears in the channel's pinned items. Get the message timestamp from get_slack_channel_history (use the ts_slack value).
unpin_slack_message2 of 2 parameters describedRemove a message from a Slack channel's pinned items. The message itself is NOT deleted — it is only removed from pinned items. Get the message timestamp from list_slack_pins or get_slack_channel_history (use the ts_slack value).
add_slack_bookmark4 of 4 parameters describedAdd a bookmark link to a channel's bookmarks bar. Max 100 bookmarks per channel. Useful for pinning important links like project docs, dashboards, or meeting notes.
add_slack_reminder3 of 3 parameters described[EXPERIMENTAL] Create a reminder for yourself or another user. Slack's reminders API has been partially deprecated since 2023 ("Save it for Later"). May become unreliable or stop working. For reliable timed messages, prefer schedule_slack_message. The 'time' parameter accepts a Unix timestamp (seconds) or natural language like "in 2 hours", "tomorrow at 9am", "next Monday".
list_slack_remindersno parameters[EXPERIMENTAL] List your Slack reminders (pending and completed). Slack's reminders API has been partially deprecated since 2023 ("Save it for Later"). May become unreliable or stop working. Returns each reminder's id — pass it to complete_slack_reminder or delete_slack_reminder to manage one.
complete_slack_reminder1 of 1 parameter described[EXPERIMENTAL] Mark a Slack reminder as complete. Get the reminder_id from list_slack_reminders.
delete_slack_reminder1 of 1 parameter described[EXPERIMENTAL] Permanently delete a Slack reminder. Get the reminder_id from list_slack_reminders. This cannot be undone.
list_slack_bookmarks1 of 1 parameter describedList the bookmarks on a channel's bookmarks bar.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.