Enables semantic search over indexed Slack channels, allowing for the retrieval of specific message threads, channel statistics, and participant lists.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@slack-indexedsearch for what was decided about the API design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
slack-indexed
MCP server for semantic search over indexed Slack channels stored in Qdrant, with Cohere reranking via AWS Bedrock.
Prerequisites
A running Qdrant instance with an indexed Slack collection (created by alaan-slack-index-mcp)
AWS credentials with access to Bedrock (Titan embeddings + Cohere rerank)
Tools
Tool | Description |
| Semantic search with Cohere reranking, filterable by source type, channel, and user |
| Retrieve all chunks for a specific Slack thread including linked resources |
| List indexed channels with document counts |
| Summary statistics (documents, threads, sources, channels) |
| List all known participant names for filtering |
Usage
Direct with uvx (no install)
Using an AWS profile:
uvx --from git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool slack-indexed --profile my-profile --qdrant-url http://localhost:6333Using explicit AWS credentials and a Qdrant API key:
uvx --from git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool slack-indexed \
--aws-access-key AKIA... \
--aws-secret-key wJal... \
--qdrant-url http://your-qdrant-host:6333 \
--qdrant-api-key your-qdrant-api-keyLocal development
uv sync
uv run slack-indexed --profile my-profile --qdrant-url http://localhost:6333Claude Code (~/.claude.json)
With AWS profile:
{
"mcpServers": {
"slack-indexed": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool",
"slack-indexed",
"--profile",
"my-profile",
"--qdrant-url",
"http://localhost:6333",
"--qdrant-api-key",
"xxxx-api-key-xxxx"
]
}
}
}With explicit AWS credentials:
{
"mcpServers": {
"slack-indexed": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool",
"slack-indexed",
"--aws-access-key",
"AKIA...",
"--aws-secret-key",
"wJal...",
"--qdrant-url",
"http://your-qdrant-host:6333",
"--qdrant-api-key",
"xxxx-api-key-xxxx"
]
}
}
}Cursor (.cursor/mcp.json)
With AWS profile:
{
"mcpServers": {
"slack-indexed": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool",
"slack-indexed",
"--profile",
"my-profile",
"--qdrant-api-key",
"xxxx-api-key-xxxx"
]
}
}
}With explicit AWS credentials:
{
"mcpServers": {
"slack-indexed": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/KanvaBhatia-Alaan/alaan-slack-index-mcp-tool",
"slack-indexed",
"--aws-access-key",
"AKIA...",
"--aws-secret-key",
"wJal...",
"--qdrant-url",
"http://your-qdrant-host:6333",
"--qdrant-api-key",
"xxxx-api-key-xxxx"
]
}
}
}CLI Options
Flag | Default | Description |
|
| Qdrant server URL |
|
| Qdrant collection name |
| (env default) | AWS profile name |
|
| AWS region for Bedrock |
| (env default) | AWS access key ID (use instead of |
| (env default) | AWS secret access key (use with |
| (none) | Qdrant API key for authenticated access |
|
| Qdrant request timeout in seconds |
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.