slack-indexed
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | AWS region for Bedrock | us-east-1 |
| profile | No | AWS profile name | |
| collection | No | Qdrant collection name | slack_index |
| qdrant-url | No | Qdrant server URL | http://localhost:6333 |
| aws-access-key | No | AWS access key ID (use instead of --profile) | |
| aws-secret-key | No | AWS secret access key (use with --aws-access-key) | |
| qdrant-api-key | No | Qdrant API key for authenticated access | |
| qdrant-timeout | No | Qdrant request timeout in seconds | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the Slack index using semantic similarity with Cohere reranking. Args: query: Natural language search query. n_results: Number of results to return (default 10, max 50). source_filter: Filter by source type. One of: slack_thread, github_issue, github_pr, github_file, linear_issue, notion_page. channel_filter: Filter by Slack channel name (partial match). user_filter: Filter by participant name (partial match on thread_users). include_links: If False, exclude linked resources and return only Slack threads. |
| get_threadA | Retrieve all chunks for a specific Slack thread, including any linked resources. Use this after search() to get the full thread context. Args: thread_ts: The thread timestamp (from search result metadata). channel_id: Optional channel ID to narrow the lookup. |
| list_channelsB | List all indexed channels and their document counts. |
| collection_statsB | Get summary statistics about the indexed collection. |
| list_usersA | List all known participants across indexed Slack threads. Scans the thread_users metadata field to return all unique participant names. Useful for discovering valid values for the user_filter parameter in search(). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: collection_stats provides overall statistics, get_thread retrieves specific thread details, list_channels and list_users enumerate available data sources, and search performs semantic queries. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern (e.g., collection_stats, get_thread, list_channels, list_users, search). The naming is uniform and predictable, with no deviations in style or convention.
With 5 tools, this server is well-scoped for its purpose of querying and exploring indexed Slack data. Each tool serves a distinct and necessary function, from high-level stats to detailed searches, without being overly sparse or bloated.
The tool set covers core workflows for exploring indexed Slack data: listing resources (channels, users), retrieving specific threads, and performing searches with filters. A minor gap is the lack of tools for updating or managing the index itself (e.g., reindexing), but this is reasonable for a read-only query interface.