Slack MCP Server vs Workstream
A side-by-side look at the Slack MCP Server and Workstream MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Slack MCP Server for communication work as a local process; choose Workstream for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Slack MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
slack_token_status, slack_health_check, slack_refresh_tokens.
Choose Workstream when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 64/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
Slack MCP Server tools 19
slack_token_statusCheck token health, age, auto-refresh status, and cache statsslack_health_checkCheck if Slack tokens are valid and show authentication statusslack_refresh_tokensForce refresh tokens by extracting from Chrome (requires Slack tab open in Chrome)slack_list_conversationsList all DMs and channels with user names resolved. Uses cached DMs by default for speed.slack_conversations_historyGet messages from a channel or DM with user names resolvedslack_get_full_conversationExport FULL conversation history with all messages, threads, and user names. Can save to file.slack_search_messagesSearch messages across the Slack workspaceslack_users_infoGet detailed information about a Slack userslack_send_messageSend a message to a channel or DMslack_get_threadGet all replies in a message threadslack_list_usersList all users in the workspaceslack_add_reactionAdd an emoji reaction to a message- +7 more on the listing page
Workstream tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Slack MCP Server
{
"mcpServers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
}
Workstream
{
"mcpServers": {
"workstream": {
"url": "http://localhost:8080/demo-insecure-token/mcp"
}
}
}
Frequently asked questions
Slack MCP Server is categorized under Communication and uses a local stdio subprocess. Workstream belongs to Communication and uses a remote HTTP/SSE transport. Pick Slack MCP Server for communication work and Workstream for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Slack MCP Server is listed as freemium — a free tier with paid plans. Auth: other. Workstream has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jtalk22-slack-mcp-server and workstream as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Slack MCP Server has a quality signal of 64/100 (Good) with 7 views, 0 installs and 31 GitHub stars. Workstream has 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
