Dmitry Korotovsky

license

MIT(OSI)

source

public

core features withheld

no

Fully MIT, no feature-gated core. The LICENSE is the plain MIT License, the whole Go server ships in the tree and installs from npm or Docker with no key, and the maintainer sells nothing beside it - no hosted tier, enterprise directory or second license.

• https://github.com/korotovsky/slack-mcp-server recorded 2026-08-13

  Repo page - MIT badge, 1,782 stargazers, the whole server in the tree. No paid tier, hosted service, license key or enterprise directory.

• https://raw.githubusercontent.com/korotovsky/slack-mcp-server/master/LICENSE recorded 2026-09-29

  The LICENSE is the plain MIT License text headed "MIT License" and "Copyright (c) 2025 Dmitrii Korotovskii".

• https://raw.githubusercontent.com/korotovsky/slack-mcp-server/master/README.md recorded 2026-09-29

  The README describes a "Model Context Protocol (MCP) server for Slack Workspaces." and closes with "Licensed under MIT - see [LICENSE](LICENSE) file." Searched the body for pricing, paid, subscription, license key and hosted: none.

Adoption is measured by npm downloads of slack-mcp-server, whose registry metadata points at korotovsky/slack-mcp-server. A same-named PyPI package is an unedited template and a different thing entirely, so only the npm figure is counted here.

• https://api.npmjs.org/downloads/point/last-month/slack-mcp-server recorded 2026-08-12

  111,307 downloads in the trailing 30 days for slack-mcp-server

Slack MCP offers a curated tool surface over one workspace, but the caller supplies the credential directly: every documented path ends with a token to find and paste, whether an OAuth token from a Slack app the caller creates or a session token extracted from the browser's own storage. The server performs no OAuth flow of its own, leaving it level with Playwright MCP.

• https://raw.githubusercontent.com/korotovsky/slack-mcp-server/master/docs/01-authentication-setup.md recorded 2026-09-17

  The authentication setup guide: "You only need one of the following: an xoxp-* User OAuth token, an xoxb-* Bot token, or both xoxc-* and xoxd-* session tokens", with the xoxc path instructing the reader to open the browser console, type "allow pasting" and run a snippet against `localStorage.localConfig_v2` to print the token. Every path ends with the caller holding a secret to configure.