Slack alternatives
6 servers that overlap with Slack. Compared on install command, provenance, and the tags they share — not on a feature checklist nobody maintains.
What these have in common
All of them overlap with Slack on at least one capability tag. Overlap is not equivalence: two servers can both say "database" and solve different problems. Read the full entry for what the current one is actually for before switching.
Side by side
| Server | Install | Source | Shared tags |
|---|---|---|---|
| Slack | npx -y @modelcontextprotocol/server-slack | Official | slack, messaging, archived |
| Slack MCP | npx -y slack-mcp-server | Community | slack, messaging, search |
| Puppeteer | npx -y @modelcontextprotocol/server-puppeteer | Official | browser, screenshots, archived |
| PostgreSQL | npx -y postgresql://localhost/mydb | Official | database, sql, archived |
| Brave Search | npx -y @modelcontextprotocol/server-brave-search | Official | search, web, archived |
| Google Maps | npx -y @modelcontextprotocol/server-google-maps | Official | maps, geo, archived |
| LINE Bot MCP | npx -y @line/line-bot-mcp-server | Official | messaging, line, bots |
How to choose
Prefer the official server when one exists, unless its install path or auth model does not fit. Prefer the smaller surface area: a server that exposes four tools you use beats one that exposes forty you do not, because every definition costs context on every request.