yt-slack-mcp
Enables reading Slack messages, permalinks, threads, and channel history, as well as replying to threads and adding reactions to messages.
Click on "Install 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., "@yt-slack-mcpPull up the Slack thread I shared earlier and summarize it."
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.
yt-slack-mcp
MCP server for Slack — read permalinks, threads, and channel history; reply to threads; add reactions.
Implements the Model Context Protocol specification: it runs over the stdio transport, speaks JSON-RPC 2.0, negotiates the protocol version on initialize, advertises tools capabilities, and describes each tool with a JSON Schema. Protocol version negotiation is handled by the @modelcontextprotocol/sdk Server class, which defaults to the latest supported version.
Tools
Tool | Description |
| Read a message or thread from a permalink (PDFs/images included) |
| Read replies for a thread by channel id + timestamp |
| Read recent channel history |
| Reply to a thread (restricted to allowed channels) |
| Add a reaction (restricted to allowed channels) |
Read tools use the private Slack browser-session API (via xoxc / xoxd tokens), so they can pull private file contents — PDFs are downloaded and text-extracted (up to 50 pages / 100k chars), images are returned inline.
Related MCP server: Slack MCP Server
Setup
1. Obtain browser session tokens
xoxc: Slack web localStorage token (from your logged-in browser session).xoxd: Slack cookie namedd.
These may need refreshing when Slack rotates/invalidates the session.
2. Place the secrets
Save each token as a single-line file:
~/.config/opencode/secrets/slack-xoxc.txt
~/.config/opencode/secrets/slack-xoxd.txtOr override the paths via the config file or env vars.
3. (Optional) Configure allowed write channels and paths
All configuration can live in a JSON config file at
~/.config/yt-slack-mcp/config.json (override with SLACK_MCP_CONFIG):
{
"secretsDir": "~/.config/opencode/secrets",
"xoxcPath": "~/.config/opencode/secrets/slack-xoxc.txt",
"xoxdPath": "~/.config/opencode/secrets/slack-xoxd.txt",
"allowedWriteChannels": ["C0123456789", "C0987654321"],
"userAgent": "Mozilla/5.0"
}By default the write tools (slack_reply_to_thread, slack_add_reaction)
are locked down — no channel is writable. Every field is optional; a
missing file just means defaults. Env vars always override the config file.
Configuration
Config resolution order: built-in defaults → config file → env vars.
Config file key | Env var | Default | Description |
|
|
| Directory holding the token files |
|
|
| Path to the |
|
|
| Path to the |
|
| (none) | Channel IDs allowed for write tools (comma-separated in env) |
|
|
| HTTP |
(config file path) |
|
| Path to the JSON config file |
MCP host config
opencode
{
"mcp": {
"slack": {
"type": "local",
"command": ["npx", "yt-slack-mcp"]
}
}
}Claude Desktop
{
"mcpServers": {
"slack": {
"command": "npx",
"args": ["yt-slack-mcp"]
}
}
}License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for Slack using User OAuth Token, enabling message management, channel operations, and user interactions via natural language.25MIT
- AlicenseNot gradedqualityBmaintenanceA production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.16,956MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Slack using a user token. It allows reading channels, DMs, threads, search, and posting messages as the authenticated user.25MIT
- AlicenseAqualityCmaintenanceMCP server that reads Slack through your own browser session, authenticating as you rather than a bot. Provides tools to search messages, retrieve channel/DM/thread history, resolve users, and post messages (write disabled by default).10MIT
Related MCP Connectors
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions.
A basic MCP server to operate on the Postman API.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yentsun/slack-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server