Slack MCP without OAuth — 21 tools, session-based, local-first. Free OSS + hosted tier from $19/mo.
Most team communication work still happens through a UI a human drives. Slack MCP server moves it into the conversation instead. Slack MCP without OAuth — 21 tools, session-based, local-first. Free OSS + hosted tier from $19/mo.
Turn Slack from an interruption stream into searchable operating memory and approved action. The open-source local path ships 21 tools today through the browser session you already have—no Slack app, scope review, or admin queue. Hosted adds permanent OAuth, indexing, scheduled intelligence, and team continuity when the workflow must run without you.
The server publishes 4 tools. What each one is for:
slack_send_message — Send to a channel or DMslack_add_reaction — Add an emoji reactionslack_remove_reaction — Remove an emoji reactionslack_conversations_mark — Mark a conversation readBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: SLACK_MCP_PROFILE, SLACK_TOKEN. 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.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Slack's toolset — slack_send_message, slack_add_reaction, slack_remove_reaction and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jtalk222; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Slack's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| slack_send_message | Send to a channel or DM |
| slack_add_reaction | Add an emoji reaction |
| slack_remove_reaction | Remove an emoji reaction |
| slack_conversations_mark | Mark a conversation read |
{
"mcpServers": {
"slack-1": {
"command": "npx",
"args": ["-y", "@jtalk22/slack-mcp"],
"env": {
"SLACK_MCP_PROFILE": "your-value",
"SLACK_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SLACK_MCP_PROFILE | Configuration value read at startup. | Optional |
| SLACK_TOKEN | Credential the server authenticates with. | Yes |
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.