A side-by-side look at the Slack MCP Server and Scrivener MCP 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 Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
slack_token_status, slack_health_check, slack_refresh_tokens.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Knowledge & Memory |
| Quality signal | 64/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 31 | 67 |
| Directory activity | 7 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 19 | Not listed |
| Full listing | View Slack MCP Server | View Scrivener MCP |
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 messageNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"jtalk22-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jtalk22/slack-mcp"
]
}
}
}
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}