Agent Comm vs Slack MCP Server
A side-by-side look at the Agent Comm 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 Agent Comm for communication work as a local process; choose Slack MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Comm when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You want tools like
comm_register, comm_agents, comm_send.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 57/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 32 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 7 | 19 |
| Full listing | View Agent Comm | View Slack MCP Server |
Tools & capabilities
Agent Comm tools 7
comm_registerRegister with name, capabilities, metadata, skills, and auto-join channelscomm_agentsAgent management — actions: `list`, `discover`, `whoami`, `heartbeat`, `status`, `unregistercomm_sendSend messages — direct (`to`), channel, broadcast, reply (`reply_to`), forward (`forward`)comm_inboxRead inbox (direct + channel messages, unread filter, `importance` filter, thread view via `thread_id`)comm_pollBlock until a new inbox message arrives (supports `timeout_ms` and `importance` filter)comm_channelChannel management — actions: `create`, `list`, `join`, `leave`, `archive`, `update`, `members`, `historycomm_stateShared key-value state — actions: `set`, `get`, `list`, `delete`, `cas
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
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.
Agent Comm
{
"mcpServers": {
"agent-comm": {
"command": "npx",
"args": [
"agent-comm"
]
}
}
}
Slack MCP Server
{
"mcpServers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
}
Frequently asked questions
Agent Comm is categorized under Communication and uses a local stdio subprocess. Slack MCP Server belongs to Communication and uses a local stdio subprocess. Pick Agent Comm 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.
Agent Comm has no declared pricing — check the project's own site. Slack MCP Server is listed as freemium — a free tier with paid plans. 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 agent-comm and jtalk22-slack-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Comm has a quality signal of 57/100 (Good) with 0 views, 0 installs and 9 GitHub stars. Slack MCP Server has 68/100 (Great) with 8 views, 0 installs and 32 GitHub stars.