Slack MCP Server for interacting with Slack workspaces via the Model Context Protocol
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"barie-slack-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Barie Slack MCP A Model Context Protocol (MCP) server for interacting with Slack workspaces. This package provides a comprehensive set of tools for managing Slack channels, messages, users, and files. ## Installation Install via `uvx`: ```bash uvx barie-slack-mcp ``` Or install via pip: ```bash pip install barie-slack-mcp ``` ## Usage Run the MCP server: ```bash barie-slack-mcp --api-token <your-slack-token> --file-storage-path <path-to-files> ``` ### Required Arguments - `--api-token`: Your Slack API token (xoxb-...) - `--file-storage-path`: Path to directory where files are stored for uploads ### Optional Arguments - `--workspace-id`: Optional workspace ID ## Features The server provides the following tools: - **Channel Management**: List, create, archive, and manage channels - **Message Operations**: Send, update, delete, and search messages - **User Management**: List and get user information - **File Uploads**: Upload files to channels - **Block Kit Support**: Send rich formatted messages using Slack Block Kit - **Team Information**: Get workspace/team details ## Requirements - Python 3.9+ - Slack API token with appropriate scopes ## Development For build and publish instructions, see [BUILD.md](BUILD.md). ## License MIT
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.