slack-readonly-mcp
Provides read-only access to Slack workspaces, including listing channels, retrieving channel history and thread replies, looking up user information, listing users, and searching messages.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@slack-readonly-mcp list the recent messages in #general"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
slack-readonly-mcp
A self-hosted, read-only Slack MCP server for Claude Code (and any MCP client).
Why this exists
Hosted Slack MCP connectors route your Slack message content through a third-party hosted MCP layer. If you care about where that data goes, that hop sits outside your control. This server avoids it:
It runs locally as a stdio subprocess that the MCP client launches.
It calls the Slack Web API directly with your own token.
Tool results flow only into your MCP client's context → whatever model endpoint you've configured (e.g. an org with zero data retention).
So the full path is: your machine → Slack API → your MCP client → your model endpoint. No third-party MCP intermediary. Data-retention guarantees are a property of the model endpoint you point the client at — this server doesn't change them, it only adds tools.
Note: Data that lives in Slack is governed by your Slack plan, not by this server. This server only governs the path between Slack and your client.
Related MCP server: Slack MCP Server
Tools (all read-only)
Tool | Purpose |
| List channels (id, name, topic, members) |
| Recent messages in a channel |
| All replies in a thread |
| Metadata for one channel |
| Look up a user (email omitted) |
| List workspace users (email omitted) |
| Search messages — requires a user token (see below) |
Setup
1. Create a Slack app with read-only scopes
At https://api.slack.com/apps → Create New App → From a manifest, paste:
display_information:
name: Claude Read-Only
oauth_config:
scopes:
bot:
- channels:read
- channels:history
- groups:read
- groups:history
- im:read
- im:history
- mpim:read
- mpim:history
- users:read
user:
- search:read # optional — only needed for slack_search_messages
settings:
org_deploy_enabled: false
socket_mode_enabled: falseInstall it to the workspace, then copy the Bot User OAuth Token (xoxb-…).
If you want search, also copy the User OAuth Token (xoxp-…). Invite the bot
to any private channels you want it to read (/invite @Claude Read-Only).
2. Build
npm install
npm run build3. Register with Claude Code
claude mcp add slack-readonly \
--env SLACK_BOT_TOKEN=xoxb-your-token \
-- node /path/to/slack-readonly-mcp/dist/index.jsOr, for a project-scoped .mcp.json (keep the token in your shell env, not in
the file — Claude Code expands ${VAR}):
{
"mcpServers": {
"slack-readonly": {
"command": "node",
"args": ["/path/to/slack-readonly-mcp/dist/index.js"],
"env": {
"SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
"SLACK_USER_TOKEN": "${SLACK_USER_TOKEN}"
}
}
}
}Search caveat
Slack's search.messages endpoint cannot be called with a bot token — it
requires a user token. Set SLACK_USER_TOKEN (xoxp-…, search:read) to enable
slack_search_messages; without it, the other six tools work and search returns
a clear error.
Notes
All logging goes to stderr; stdout is the JSON-RPC channel.
The server fails fast (exit 1) if
SLACK_BOT_TOKENis unset.Read-only by design. Adding write tools (post/reply/react) means adding write scopes — a deliberately separate, larger-blast-radius change.
License
MIT
Available Tools
7 toolsslack_channel_historyA
Read recent messages from a Slack channel (read-only). Provide the channel id (e.g. C0123ABCD), not the name — resolve names via slack_list_channels first.
Inputs: channel (required), limit, oldest, latest, +1 more.
slack_conversations_infoA
Get metadata for a single Slack channel by id (read-only): name, topic, purpose, member count, archived state.
Inputs: channel (required).
slack_list_channelsA
List Slack channels the bot can see (read-only). Returns each channel's id, name, topic, and member count. Use the returned id with slack_channel_history — most other tools take an id (C0123ABCD), not a name.
Inputs: types, limit, cursor.
slack_list_usersA
List Slack workspace users (read-only). Returns id, name, real name, and bot flag. Email is intentionally omitted.
Inputs: limit, cursor.
slack_search_messagesA
Search messages across the workspace (read-only). Requires a user token (SLACK_USER_TOKEN with search:read) — bot tokens cannot search. Supports Slack search operators like in:#channel, from:@user, before:YYYY-MM-DD.
Inputs: query (required), count, page.
slack_thread_repliesA
Read all replies in a Slack thread (read-only). Provide the channel id and the parent message's ts (thread_ts).
Inputs: channel (required), ts (required), limit, cursor.
slack_user_infoA
Look up a Slack user by id (read-only). Returns display name, real name, and timezone. Email is intentionally omitted.
Inputs: user (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: listing vs single item, history vs search, threads vs general messages, users vs user info. No overlap.
All tools follow the consistent 'slack_verb_noun' pattern (e.g., slack_list_channels, slack_user_info). Minor variation between 'channel_history' and 'conversations_info' but both are noun phrases in the same style.
7 tools is well-scoped for a read-only Slack server, covering channel exploration, history, threads, user info, and search without being excessive.
Covers core read operations (channel list, history, threads, users, search). Minor gaps like reading pinned messages or files, but these are less critical for a read-only interface.
Maintenance
Related MCP Connectors
Hosted Slack MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.
Hosted WhatsApp MCP server: read, search and reply to your own WhatsApp chats from your AI.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides read-only access to Slack data including messages, channels, and users through secure API endpoints.MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables AI assistants to access Slack workspace data, including channels, messages, threads, and user information.3MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for Slack with OAuth 2.1 authentication, enabling message retrieval, thread replies, search, user and channel listing.9Apache 2.0
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for Slack using User OAuth Token, enabling message management, channel operations, and user interactions via natural language.156 npmMIT