This MCP server allows AI agents to access Slack without app registration, admin approval, or OAuth, using browser session tokens instead. It provides 16 tools for various Slack interactions.
From the registry: Slack MCP for self-host or managed Cloud, with Gemini CLI and secure-default HTTP.

Please install the `slack-mcp-server` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js 20+** — Node.js 20 or later required (https://nodejs.org)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@jtalk22/slack-mcp"]
- optional environment variables:
- `SLACK_TOKEN`: Slack session token (xoxc-). Required on Windows/Linux. On macOS, auto-extracted from Chrome. (example: `xoxc-<your_token>`)
- `SLACK_COOKIE`: Slack session cookie (xoxd-). Required on Windows/Linux. On macOS, auto-extracted from Chrome. (example: `xoxd-<your_cookie>`)
Note: Uses browser session tokens (xoxc-/xoxd-), not official OAuth. Run 'npx -y @jtalk22/slack-mcp --setup' for interactive setup wizard. On macOS, tokens auto-extracted from Chrome. 16 tools total (12 read-only, 4 write).
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.SLACK_TOKENrequiredToken for accessing SlackSLACK_COOKIErequiredCookie for accessing SlackLightweight DMARC parser: auto-fetch email reports, visualize compliance in a single all-in-one app