{"id":"ubie-oss-slack-mcp-server","name":"slack-mcp-server","af_score":50.5,"security_score":59.0,"reliability_score":26.2,"what_it_does":"Slack MCP server exposing Slack Web API capabilities as MCP tools, supporting both local stdio transport and remote HTTP transport.","best_when":"You want an MCP-compatible integration to let an AI agent read and/or act in a Slack workspace using standardized tool calls.","avoid_when":"You cannot safely handle OAuth tokens or you lack control over what the agent is allowed to do (e.g., broad write capabilities like posting/reactions/search across the workspace).","last_evaluated":"2026-03-30T13:45:43.798477+00:00","has_mcp":true,"has_api":true,"auth_methods":["Slack Bot User OAuth token (SLACK_BOT_TOKEN)","Slack User OAuth token (SLACK_USER_TOKEN)"],"has_free_tier":false,"known_gotchas":["Write-capable tools (post message, add reaction, reply) may have side effects; agents should implement their own safeguards (confirmations, idempotency via message dedupe, etc.).","Message search may depend on Slack user token and safe-search behavior; agents should expect different results depending on token and SLACK_SAFE_SEARCH setting.","HTTP transport is started locally on a port; ensure networking/auth boundaries around the server since the README does not describe additional request authentication."],"error_quality":0.0}