Slack MCP Server for Claude

Content

Slack MCP Server is Slack's official remote Model Context Protocol server. It lets Claude and other compatible MCP clients search Slack, retrieve messages, read channels and threads, send or draft messages, create conversations, add reactions, manage canvases, and inspect users through Slack-managed OAuth and workspace-admin approval.

Slack documents the transport endpoint as:

https://mcp.slack.com/mcp

The server uses JSON-RPC 2.0 over Streamable HTTP. Slack's docs explicitly note that SSE-based connections and Dynamic Client Registration are not supported at this time, so use a client that supports Slack's current remote MCP/OAuth path.

Source Review

• https://docs.slack.dev/ai/slack-mcp-server/
• https://slack.com/help/articles/48855576908307-Guide-to-the-Slack-MCP-server
• https://docs.slack.dev/changelog/2026/05/13/new-mcp-tools/

These sources were reviewed on 2026-06-04. Prefer the live Slack docs over model memory for endpoint behavior, OAuth metadata, available clients, app identity requirements, scopes, rate limits, and tool coverage.

Features

• Official Slack-hosted MCP server at https://mcp.slack.com/mcp.
• Streamable HTTP transport with JSON-RPC 2.0.
• OAuth-backed user-token flow using Slack OAuth endpoints and client-specific authorization UX.
• Workspace-admin managed approval for MCP client integrations.
• Search tools for messages, files, users, public channels, private channels, channel descriptions, and emoji.
• Message tools for reading channels, reading threads, sending messages, drafting messages, creating conversations, and adding reactions.
• Canvas tools for creating, updating, reading, and exporting canvases as markdown.
• User tools for reading complete user profile information, custom profile fields, statuses, and channel membership.
• Slack Web API rate-limit behavior by MCP tool/action type.
• Support path through partner-built clients such as Claude.ai, Claude Code, Perplexity, and Cursor as listed by Slack.

Use Cases

• Ask Claude to find prior decisions, release context, customer feedback, or incident history across approved Slack channels.
• Summarize long channels or threads before a follow-up meeting.
• Draft a status update, release note, incident note, or team announcement for human review before posting.
• Create a project channel or group conversation after a human confirms the audience and name.
• Add reactions to acknowledge specific workflow events in low-risk channels.
• Create or update canvases that summarize research, sprint plans, runbooks, or project notes.
• Inspect user profiles or channel membership when routing questions to the right team.
• Combine Slack context with other read-only tools after reviewing cross-tool data movement.

Installation

Claude Code

Add the remote MCP server with HTTP transport:

claude mcp add --transport http slack https://mcp.slack.com/mcp

Then follow your client's Slack OAuth flow and any workspace-admin approval steps. Verify the server appears in the MCP list:

claude mcp list

Claude Desktop or Other MCP Clients

Use the client-specific remote HTTP MCP configuration format. A generic shape is:

{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.slack.com/mcp",
      "transport": "http"
    }
  }
}

Restart or reconnect the client, complete Slack OAuth, and verify the scopes and workspace approval status before asking the assistant to read or write Slack content.

Requirements

• Slack workspace and user account.
• Admin-approved MCP client integration or permission to request approval.
• Supported MCP client with remote HTTP transport and Slack OAuth support.
• OAuth client/app identity path that satisfies Slack's fixed app ID requirements.
• User-token scopes matching the tools you intend to use.
• Network access to https://mcp.slack.com/mcp.
• Workspace data-governance policy covering AI access to public channels, private channels, DMs, files, canvases, and user profiles.
• Rate-limit and human-review policy for searches, message writes, reactions, conversation creation, and canvas changes.

Configuration

{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.slack.com/mcp",
      "transport": "http"
    }
  }
}

For managed workspaces, confirm with Slack admins which app/client is approved, which scopes are enabled, and whether audit logs are being reviewed for MCP activity.

Security And Privacy Review

• Start with the smallest scopes that satisfy the workflow. Avoid granting DMs, private channels, files, canvases, user email, or write scopes until the use case requires them.
• Treat message posting and canvas edits as production writes. Ask the assistant to draft first, then require a human to approve the exact target conversation and message.
• Avoid prompts that ask the assistant to sweep all channels, enumerate private spaces, or summarize unrelated personal conversations.
• Use Slack audit logs and app-management views to review MCP activity where your plan supports it.
• Keep Slack context out of public issues, PR bodies, screenshots, logs, and downstream tools unless the content owner approved sharing.
• Review cross-server flows before combining Slack with GitHub, Jira, Linear, databases, browsers, filesystems, or shell tools.

Troubleshooting

• OAuth fails: verify that the MCP client supports Slack's current OAuth flow, the app/client is approved for the workspace, and the user has access to the requested scopes.
• Client cannot connect: confirm it supports Streamable HTTP MCP and is configured with https://mcp.slack.com/mcp, not an SSE endpoint.
• Tool is missing or denied: check the OAuth scopes enabled for the user token and whether the workspace admin approved that capability.
• Search returns too little: confirm channel membership, private-channel access, search scopes, and date/user/content filters.
• Writes are unexpectedly broad: require draft-first workflows and verify channel, DM, canvas, or conversation targets before execution.
• Rate limits appear: narrow the search, batch requests intentionally, and avoid repeated autonomous loops over channels or threads.

Duplicate Check

• No existing upstream content file uses the slack-mcp-server slug, Slack MCP endpoint, or official Slack MCP documentation URLs.
• Existing Slack notifier hooks and generic Slack mentions remain distinct because this entry covers Slack's official remote MCP server, OAuth scopes, Streamable HTTP endpoint, Slack tools, admin approval, and Slack-specific data governance.

Editorial Disclosure

This is a source-backed community content entry submitted by oktofeesh1. There is no paid placement, affiliate link, sponsorship, or maintainer-verified package artifact attached to this listing.