Slack MCP Server

If you already use Slack, the slack mcp server is the piece that lets your assistant work with it directly. Full read + write access to Slack Lists for AI: create, update, check off, reassign, delete.

What the server does

This server acts as a bridge between AI models and Slack, enabling seamless creation, retrieval, updating, deletion, filtering, and management of Slack List items through a standardized protocol. It empowers AI assistants like Claude Desktop to become powerful productivity tools for managing tasks, projects, and data within Slack.

• Create Single Item — Add one item to a list with detailed fields
• Bulk Create Items — Add multiple items at once with built-in rate limiting to respect Slack's API
• Retrieve Items — Fetch a list of items with optional metadata
• Update Items — Update any cell on an existing item — check a task off, reassign it, reschedule it, or edit any field (full task management)
• Delete Items — Permanently remove an item from a list
• Discover Columns — Infer a list's column IDs, types, and select option IDs from its existing items (Slack exposes no schema API, so this saves you from hunting for IDs in browser dev tools)

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• lists — read
• text — String value
• date — String in YYYY-MM-DD format
• user — Array of Slack user IDs (e.g., ["U1234567"])
• select — Array of select option IDs
• checkbox — Boolean true or false
• number — Numeric value
• email — String email address
• phone — String phone number
• contains — Field contains the value (case-insensitive)
• equals — Field exactly matches the value (case-insensitive)
• not_equals — Field does not match the value

Credentials and setup notes

Configuration is passed through the environment: SLACK_BOT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10+ - Slack Workspace: A Slack workspace where you have permission to install apps. - Slack Bot Token: A bot token with lists:read and lists:write scopes.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Slack's toolset — lists, text, date and 11 more — is a fair guide to whether it matches your workflow. It is maintained by justadityaraj; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Slack.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.