Collaboration Platform Data Retrieval Endpoint (MCP Server)

This Model Context Protocol (MCP) server furnishes the necessary functionalities to leverage Slack's native search and enumeration capabilities. It enables Large Language Models (LLMs) to query and secure various data artifacts, including user directories, channel manifests, message histories, and dialogue sequences, residing within a specific Slack organizational unit.

Integrated Functions (Tools)

1. get_users - Enumerates and returns the complete roster of active workspace members.
2. get_channels - Yields a comprehensive inventory of all defined communication channels.
3. get_channel_messages - Fetches the message log for a specified communication channel.
4. get_thread_replies - Retrieves the nested responses belonging to a particular message thread.
5. search_messages - Executes a targeted query against message content across the workspace.

Abstracted Access Points (Resources)

1. allusers:// - Direct URI for fetching the entirety of the workspace user registry.
2. allchannels:// - Direct URI for fetching the entirety of the workspace channel registry.

Prerequisites

• Execution requires the Bun runtime environment.
• A valid Slack API authentication credential (token) possessing requisite access scopes is mandatory.

Deployment Protocol

1. Obtain a copy of the source repository.
2. Install necessary external dependencies: bash bun install

Execution Instructions

1. Configure the Slack Access Credential via environment variable assignment: bash export SLACK_TOKEN=xoxb-your-token-here

2. Initiate the server process: bash bun run index.ts

   Alternatively, utilize the pre-compiled binary: bash ./dist/slack_search_function_mcp

Compilation Process

To generate the standalone executable:

bash bun run build

This action culminates in a self-contained executable file located within the dist directory.

MCP Integration Specification

To incorporate this retrieval endpoint into an MCP-aware LLM architecture, integrate the following configuration block into your primary MCP manifest:

{ "mcpServers": { "slack": { "command": "/path/to/dist/slack_search_function_mcp", "env": { "SLACK_TOKEN": "xoxb-your-token-here" } } } }

Exemplary Tool Invocation Schemas

User Roster Retrieval

{ "name": "get_users", "arguments": { "limit": 10 } }

Channel Manifest Request

{ "name": "get_channels", "arguments": { "limit": 10, "exclude_archived": true } }

Channel Dialogue Fetch

{ "name": "get_channel_messages", "arguments": { "channel": "C01234ABCDE", "limit": 10 } }

Threaded Response Acquisition

{ "name": "get_thread_replies", "arguments": { "channel": "C01234ABCDE", "thread_ts": "1234567890.123456", "limit": 10 } }

Content Search Operation

{ "name": "search_messages", "arguments": { "query": "important announcement", "sort": "timestamp", "sort_dir": "desc", "count": 10 } }

Abstracted Access Point Usage

Full User Registry Access

allusers://

Full Channel Registry Access

allchannels://

Exception Management

The operational server incorporates robust error governance for scenarios including: - Absence or invalidity of the Slack Access Credential. - Exceeding prescribed API transmission quotas (rate limiting). - Disruptions in network connectivity. - Submission of parameters violating expected schema. - Failures related to authorization verification.

Security Posture

• The Slack API credential is never persisted to logs or transmitted in output payloads.
• Secure injection of the token is enforced exclusively via process environment variables.