What authentication does Slack MCP Server use?
It uses a Slack User OAuth Token (starting with `xoxp-`) instead of a bot token, allowing access to direct messages and sending messages on behalf of the user.
@AIAtrium
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"slack-mcp-server-aiatrium": {
"command": "docker",
"args": [
"build",
"-t",
"mcp/slack",
"-f",
"src/slack/Dockerfile",
"."
]
}
}
}List of channels with their IDs and information
Message posting confirmation and timestamp
Reply confirmation and timestamp
Reaction confirmation
List of messages with their content and metadata
List of replies with their content and metadata
List of users with their basic profiles
Detailed user profile information
A Model Context Protocol server that integrates with the Slack API using a user token, enabling Claude to read and send messages, list channels, and access user profiles in Slack workspaces. It is forked from the official MCP Slack server and swaps bot token authentication for a user token to support a wider range of use cases, including direct messages.
Create a Slack app with specific user token scopes, install it to your workspace, obtain a User OAuth Token starting with xoxp-, and run npm install. Then configure Claude Desktop by adding the NPX or Docker command to claude_desktop_config.json with the SLACK_USER_TOKEN environment variable set.
It uses a Slack User OAuth Token (starting with `xoxp-`) instead of a bot token, allowing access to direct messages and sending messages on behalf of the user.
The required user token scopes are: `channels:history`, `channels:read`, `chat:write`, `reactions:write`, `users:read`, `users.profile:read`, `groups:history`, `groups:read`, `groups:write`, `im:history`, `im:read`, `im:write`, `mpim:history`, `mpim:read`, and `mpim:write`.
Add a configuration entry to `claude_desktop_config.json` using the NPX command (`npx -y @modelcontextprotocol/server-slack`) or Docker, and set the `SLACK_USER_TOKEN` environment variable to your user token.
The server exposes eight tools: `slack_list_channels`, `slack_post_message`, `slack_reply_to_thread`, `slack_add_reaction`, `slack_get_channel_history`, `slack_get_thread_replies`, `slack_get_users`, and `slack_get_user_profile`.
Permission errors usually occur if required scopes are missing, the app isn't fully installed to the workspace, the token or workspace ID is incorrect, or the app hasn't been added to the target channels.

Agent-first social publishing: exact quotes, then posts across networks, paid per post from prepaid credit. Remote MCP. Preview: quotes and sandbox posts now; live posts soon. By Novus Index LLC.

Official Mobile Text Alerts server. Send and schedule SMS, manage subscribers and groups, and complete carrier registration from any MCP-compatible AI assistant.

Agencies and GTM teams use HeyReach and Instantly to run LinkedIn outbound from personal sender profiles — but those profiles sit empty and prospects don't accept. B2B Creators is the content layer that keeps every sende

MCP server and API for AI agents that work LinkedIn on accounts you own: search, connect, message and enrich, with limits enforced on our server.

Send birthday cards, Christmas cards and postcards, printed and mailed for you.
Comments