Workstream vs Slack MCP Server
A side-by-side look at the Workstream and Slack MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Workstream for communication work over a hosted endpoint; choose Slack MCP Server 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 Workstream when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Choose Slack MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You want tools like
UserID, UserName, RealName.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 36/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Workstream tools
No tool names declared yet. Check the project README from the listing page.
Slack MCP Server tools 7
UserIDUser ID (e.g., `U1234567890`)UserNameSlack usernameRealNameUser's real nameDisplayNameUser's display nameEmailUser's email addressTitleUser's job titleDMChannelIDDM channel ID if available in cache (for quick messaging)
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.
Workstream
{
"mcpServers": {
"workstream": {
"url": "http://localhost:8080/demo-insecure-token/mcp"
}
}
}
Slack MCP Server
{
"mcpServers": {
"korotovsky-slack-mcp-server": {
"url": "https://api.slack.com/changelog/2023-07-its-later-already-for-stars-and-reminders"
}
}
}
Frequently asked questions
Workstream is categorized under Communication and uses a remote HTTP/SSE transport. Slack MCP Server belongs to Communication and uses a remote HTTP/SSE transport. Pick Workstream for communication work and Slack MCP Server 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.
Workstream has no declared pricing — check the project's own site. Slack MCP Server is listed as free. Auth: other. 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 workstream and korotovsky-slack-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Workstream has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Slack MCP Server has 51/100 (Good) with 2 views, 0 installs and 1,864 GitHub stars.
