Slack Search
The Slack Search MCP server provides AI assistants with direct access to Slack workspace data through a set of tools and resources for retrieving users, channels, messages, and performing searches. Built with TypeScript and Bun runtime, it implements five core tools (get_users, get_channels, get_channel_messages, get_thread_replies, and search_messages) and two resource endpoints (allusers:// and allchannels://) that handle pagination automatically. The implementation features comprehensive error handling for API rate limits, network issues, and authentication failures, making it particularly valuable for AI assistants that need to reference or search through Slack conversations without requiring direct Slack API access themselves.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.
Scan details: Circle-IR · 2026-09-02 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- communication
- Source
- PulseMCP
- Author type
- human
- Last scanned
- 2026-09-02
- Updated
- 2026-09-02
Use via MCP
Resolve Slack Search from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.