Slack (local)
BetaA Slack server that reads channels and messages and posts for the developer with a bot token. The MCP project's package is archived but still widely run.
- Local
- Runs
- On the developer's Mac
- Launched with
- npx, Docker
- Platform
- macOS
- Publisher
- Model Context Protocol (archived)
How it works
Every agent request passes through Ferentin policy before it reaches Slack (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @modelcontextprotocol/server-slack or docker run -i --rm mcp/slack.
Ferentin's endpoint agent finds Slack (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Slack (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Slack (local)
A Slack server that reads channels and messages and posts for the developer with a bot token. The MCP project's package is archived but still widely run.
Frequently asked about Slack (local)
- How do I connect Slack (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Slack (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Slack (local) integration generally available?
- The Slack (local) integration is currently beta on Ferentin.
