$ loading_
Search Slack channels, messages, threads, reactions, files, and scheduled messages.
This Slack MCP tool comes from an official registry and is open source, making its overall provenance relatively trustworthy. Its main security considerations are typical for this class of integration tools: it requires Slack OAuth credentials, may access workspace messages/files, and runs a local service process; no explicit high-risk red flags are evident in the provided materials.
It requires sensitive Slack OAuth-related parameters such as SLACK_TEAM_ID, SLACK_CLIENT_ID, and SLACK_CLIENT_SECRET. If the config file or environment variables are exposed, they could enable unauthorized access to the Slack workspace APIs. Other settings like timeout/retry values are less sensitive.
No fixed remote host is listed in the materials, but as a Slack integration tool, its stated functionality around channels, messages, threads, files, and users would typically involve communicating with Slack services and sending related data off the local machine. There is no evidence here of exfiltration to unknown or unrelated endpoints.
The system checks indicate that this tool executes code/runs a process, which is normal for MCP tools. The provided materials do not show requests for unusual system privileges, nor do they describe local execution capabilities beyond its stated Slack integration purpose.
By description, it can handle channels, messages, threads, reactions, users, files, and scheduled messages, implying potentially broad access to Slack workspace content. It also requires SLACK_CONFIG_PATH, so it will at least access a local config file. Based on the available materials, this scope appears broadly aligned with its stated functionality, with no clear evidence of excessive privilege.
The source is an official registry entry and has an auditable open-source repository, with updates within the last year; these are positive indicators that reduce risk. While the repository has low star count and no declared license, which adds some adoption and compliance uncertainty, that is not enough to make it high risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Slack" MCP server from askskill: Run: claude mcp add 'io-github-mindstone-mcp-server-slack' -- npx -y @mindstone/mcp-server-slack
Access and manage Salesforce CRM records, tasks, opportunities, and custom objects.
Connect Gmail, Calendar, Drive, and Docs for streamlined work automation.
Manage TalentLMS users, courses, groups, branches, reports, and assessments.
Build and manage voice call agents with LLM integration and voice discovery.
Connect Microsoft 365 mail to read, search, draft, and manage emails.
Automate browser actions like navigation, form filling, clicking, screenshots, and tab management.
Search Slack, read channel history, inspect users, and send messages safely.
Access Slack read-only data to search messages, threads, users, and channels.
Connect AI to Slack for messaging, channel management, users, and file uploads.
Let AI access Slack data to search conversations and support collaboration.
Let AI manage Slack messages, threads, channels, and user info.
Let AI assistants read, search, and interact with Slack workspaces.