SlackSAFE
A Model Context Protocol Server for Interacting with Slack
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
This is a connector to allow Claude Desktop (or any MCP client) to interact with your Slack workspace to post messages and query a list of all users.
Local Development
In order to run this client locally, add the following configuration to your Claude Desktop MCP Server config file:
{
"mcpServers": {
"mcp-slack-local": {
"command": "node",
"args": ["/path/to/project/dist/index.js"], <---- replace this with your project path
"env": {
"SLACK_BOT_USER_OAUTH_TOKEN": "test-bot-token",
"SLACK_TEAM_ID": "test-team-id"
}
},
}
}After this, you should be able to test this implementation in your Claude Desktop App using example prompts like:
- "Can you list all users of my Slack team?"
- "Can you send a welcome message to my Slack Channel with the ID ``?"
Running the server locally:
node dist/index.js
With the build in another terminal
npm run watch
Slack Permission Scopes
The following permissions are already implemented:
1696e2613df9OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add slack-model-context-protocol-server --env SLACK_BOT_USER_OAUTH_TOKEN=${SLACK_BOT_USER_OAUTH_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"slack-model-context-protocol-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SLACK_BOT_USER_OAUTH_TOKEN": "${SLACK_BOT_USER_OAUTH_TOKEN}"
}
}
}
}Exposed tools (2)
1 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
slack_get_users | read | Get a list of all users in the workspace with basic information |
slack_post_message | write | Post a new message to a Slack channel |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
@types/node, shx, typescript
Gates applied: no_behavioural_pass, no_license.
1696e2613df9full audit observations/trust-audit/mcp-server/avimbu__slack.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 1696e2613df9 | SAFE | B | 89 | first audit |
Questions
What is the Slack MCP server?
A Model Context Protocol Server for Interacting with Slack
What tools does Slack expose?
2 in total: 1 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Slack safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Slack need?
It reads SLACK_BOT_USER_OAUTH_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Slack run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as slack-model-context-protocol-server at 0.0.1.
How current is this page?
The grade is for one exact copy of the source (1696e2613df9), read on 2026-10-09. The repository is watched and re-audited when it changes.