A Slack MCP server
A Slack MCP server. Exposed over MCP by the slack mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A MCP(Model Context Protocol) server for accessing Slack API. This server allows AI assistants to interact with the Slack API through a standardized interface.
Everything the assistant can do here goes through one of these:
Installation — NOTE: Its now hosted in GitHub Registry so you need your PATConfiguration — You can also create a .env file to set these environment variables:Usage — The Usage tool exposed by this serverContributing — 1. Fork the repository 2. Create your feature branch 3. Run tests and linting: npm run lint 4. Commit your changes 5. Push to the branch 6. Create aBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 3 environment variables: SLACK_BOT_TOKEN, SLACK_USER_TOKEN, SLACK_SAFE_SEARCH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Slack's toolset — Installation, Configuration, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ubie-oss; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Installation | NOTE: Its now hosted in GitHub Registry so you need your PAT. |
| Configuration | You can also create a .env file to set these environment variables: |
| Usage | The Usage tool exposed by this server. |
| Contributing | 1. Fork the repository 2. Create your feature branch 3. Run tests and linting: npm run lint 4. Commit your changes 5. Push to the branch 6. Create a Pull Request |
{
"mcpServers": {
"slack-mcp-server-ubie-oss": {
"command": "npx",
"args": ["-y", "@ubie-oss/slack-mcp-server"],
"env": {
"SLACK_BOT_TOKEN": "your-value",
"SLACK_USER_TOKEN": "your-value",
"SLACK_SAFE_SEARCH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SLACK_BOT_TOKEN | Credential the server authenticates with. | Yes |
| SLACK_USER_TOKEN | Credential the server authenticates with. | Yes |
| SLACK_SAFE_SEARCH | 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.