MCP server for interacting with Slack as a user
MCP server for interacting with Slack as a user. That is what the slack user mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP Server for the Slack API, enabling Claude to interact with Slack workspaces as a user.
This on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 2 tools. What each one is for:
Returns — List of channels with their IDs and informationTroubleshooting — If you encounter permission errors, verify that: 1. All required scopes are added to your Slack app 2. The app is properly installed to yourConfiguration is passed through the environment: SLACK_TOKEN, SLACK_TEAM_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Slack User MCP's toolset — Returns, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by lars-hagen; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Returns | List of channels with their IDs and information |
| Troubleshooting | If you encounter permission errors, verify that: 1. All required scopes are added to your Slack app 2. The app is properly installed to your workspace 3. The token and, when needed, workspace ID are correctly copied to y |
Then configure Claude Desktop:
```json
{
"mcpServers": {
"slack": {
"command": "npm",
"args": [
"run",
"--prefix",
"/path/to/slack-user-mcp",
"start"
],
"env": {
"SLACK_TOKEN": "xoxp-your-user-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SLACK_TOKEN | Credential the server authenticates with. | Yes |
| SLACK_TEAM_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.