$ loading_
Manage messages, channels, search, and threads across multiple Slack workspaces.
This tool claims to provide messaging, channels, search, and threads across multiple Slack workspaces. It is open-source under MIT and does not declare extra environment variables or fixed remote endpoints, but its core function inherently involves accessing and operating on Slack data, so the overall posture is caution rather than clear high risk. The main concerns are missing documentation, low community adoption, and unknown maintenance status, which reduce auditability and source confidence.
The material states there are no keys/environment variables, but a tool that operates across multiple Slack workspaces would normally require some form of Slack authorization or session context in practice. Due to missing documentation, credential acquisition, storage, and permission boundaries are unclear, creating moderate uncertainty around credential misuse.
No fixed remote host is declared, but based on the stated functionality, it would likely need to interact with Slack services, meaning user messages, search content, and thread data would likely be sent to Slack-related endpoints. There is no explicit red flag of exfiltration to unrelated or unknown third-party endpoints, but data-flow disclosure is insufficient.
The system checks indicate that this MCP tool can execute code or start processes locally; this is a common MCP capability and by itself does not justify a high-risk rating. The material does not show requests for extra system privileges clearly unrelated to Slack integration, but the missing README prevents detailed verification of the exact local capabilities exposed.
Per the description, the tool can access messages, channels, search results, and threads across multiple Slack workspaces, which may cover a broad set of historical communications. There is no explicit claim that it reads or writes sensitive local files or seeks data access beyond the Slack use case, but the lack of documentation means least-privilege design cannot be confirmed.
Positive factors include an auditable open-source repository and an MIT license, which materially reduce the kind of risk associated with closed-source exfiltration. Negative factors are that the source is only a third-party registry entry, the GitHub project has 0 stars, maintenance status is unknown, and the README is missing, so supply-chain maturity and maintenance signals are weak and warrant caution.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Slack MCP Server" yet — see the docs or source repo.
Search all connected Slack workspaces for “Q4 launch plan” and summarize the most relevant channels, message links, and key takeaways.
A cross-workspace results list with concise summaries and links to the original messages.
Review important threads from the past 7 days in #product-launch and extract action items, owners, and deadlines into a checklist.
A structured action-item list grouped by source thread for easy follow-up.
Based on today’s development progress, draft and send a concise professional project update to #engineering-updates including completed work, risks, and next steps.
A ready-to-send status update posted to the specified Slack channel.
Connect AI to Slack for messaging, channel management, users, and file uploads.
Let AI assistants read, search, and interact with Slack workspaces.
Access Slack read-only data to search messages, threads, users, and channels.
Let AI access Slack data to search conversations and support collaboration.
Integrate Slack via MCP tools and webhooks for collaboration and automation.
Let AI manage Slack messages, threads, channels, and user info.