A Model Context Protocol (MCP) server that enables LLMs to interact with Slack workspaces through OAuth 2.0 authentication.
Study Slack Remote MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server that enables LLMs to interact with Slack workspaces through OAuth 2.0 authentication.
Once Study Slack Remote MCP is connected, these are the calls the assistant has available:
channel_id — Channel ID (required)text — Message text (required)Testing — The Testing tool exposed by this serverDebugging — Enable debug logging by checking server.log: bash tail -f server.logSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 3 environment variables: SLACK_CLIENT_ID, SLACK_CLIENT_SECRET, SERVICE_BASE_URL. 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. Study Slack Remote MCP's toolset — channel_id, text, Testing and 1 more — is a fair guide to whether it matches your workflow. It is maintained by miyatsuki; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| channel_id | Channel ID (required) |
| text | Message text (required) |
| Testing | The Testing tool exposed by this server. |
| Debugging | Enable debug logging by checking server.log: bash tail -f server.log |
{
"mcpServers": {
"slack": {
"command": "uv",
"args": [
"--directory",
"/path/to/slack-mcp-server",
"run",
"python",
"server.py"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SLACK_CLIENT_ID | Configuration value read at startup. | Optional |
| SLACK_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SERVICE_BASE_URL | Endpoint or connection string the server talks to. | 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.