Slack

Remote MCP server for Slack messages, channels, users, canvases, and collaboration context.

Connection specification

Remote endpoint
https://mcp.slack.com/mcp
Browser access
Not yet measured
Declared MCP transport
Streamable HTTP
Live-validated MCP transport
Not yet verified — Latest validation did not verify a transport
Declared authentication
OAuth 2.1
Detected authentication
OAuth 2.1 detected or retained from publisher evidence
Protocol lifecycle
Not yet negotiated
Authorization server
https://mcp.slack.com
Category
Communication

Product documentation · Official listing documentation

Provider guidance

  • Browser OAuth requires the mcptest operator's SLACK_OAUTH_CLIENT_ID and SLACK_OAUTH_CLIENT_SECRET Worker bindings. Production readiness must not be claimed until both are configured.

Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

mcptest operator setup required

This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.

Publisher evidence reviewed .

Client ID
Required
Client secret
Required — never enter it in a browser
Browser/public client
Not supported

Required non-secret settings

Application owner
mcptest operator (required)
Distribution
Internal workspace or published app as applicable (required)

Callback URIs

  • https://mcptest.io/oauth/callback

Provider setup steps

  1. The mcptest operator creates and owns the Slack application.
  2. Configure the app for the workspace or published distribution required by Slack.
  3. Register the exact hosted mcptest callback URI.
  4. Store the client ID and client secret only in operator-controlled server bindings.

Open provider setup or application page

Publisher documentation

Connect this server to your client

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

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

mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.

  • Using live-validated endpoint: https://mcp.slack.com/mcp
  • mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.
  • Provider setup: The mcptest operator creates and owns the Slack application.
  • Provider setup: Configure the app for the workspace or published distribution required by Slack.
  • Provider setup: Register the exact hosted mcptest callback URI.
  • Provider setup: Store the client ID and client secret only in operator-controlled server bindings.
  • Publisher evidence (reviewed 2026-08-24): https://docs.slack.dev/ai/slack-mcp-server/
  • Provider guidance: Browser OAuth requires the mcptest operator's SLACK_OAUTH_CLIENT_ID and SLACK_OAUTH_CLIENT_SECRET Worker bindings. Production readiness must not be claimed until both are configured.

Claude Code MCP documentation

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'slack' --url 'https://mcp.slack.com/mcp'

mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.

  • Using live-validated endpoint: https://mcp.slack.com/mcp
  • mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.
  • Provider setup: The mcptest operator creates and owns the Slack application.
  • Provider setup: Configure the app for the workspace or published distribution required by Slack.
  • Provider setup: Register the exact hosted mcptest callback URI.
  • Provider setup: Store the client ID and client secret only in operator-controlled server bindings.
  • Publisher evidence (reviewed 2026-08-24): https://docs.slack.dev/ai/slack-mcp-server/
  • Provider guidance: Browser OAuth requires the mcptest operator's SLACK_OAUTH_CLIENT_ID and SLACK_OAUTH_CLIENT_SECRET Worker bindings. Production readiness must not be claimed until both are configured.

Codex MCP documentation

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

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

mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.

  • Using live-validated endpoint: https://mcp.slack.com/mcp
  • mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.
  • Provider setup: The mcptest operator creates and owns the Slack application.
  • Provider setup: Configure the app for the workspace or published distribution required by Slack.
  • Provider setup: Register the exact hosted mcptest callback URI.
  • Provider setup: Store the client ID and client secret only in operator-controlled server bindings.
  • Publisher evidence (reviewed 2026-08-24): https://docs.slack.dev/ai/slack-mcp-server/
  • Provider guidance: Browser OAuth requires the mcptest operator's SLACK_OAUTH_CLIENT_ID and SLACK_OAUTH_CLIENT_SECRET Worker bindings. Production readiness must not be claimed until both are configured.

Cursor MCP documentation

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "slack": {
      "type": "http",
      "url": "https://mcp.slack.com/mcp"
    }
  }
}

mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.

  • Using live-validated endpoint: https://mcp.slack.com/mcp
  • mcptest operator setup required: This provider requires a confidential application managed by the mcptest operator. Its client secret and token exchange stay server-side and must never be pasted into a browser.
  • Provider setup: The mcptest operator creates and owns the Slack application.
  • Provider setup: Configure the app for the workspace or published distribution required by Slack.
  • Provider setup: Register the exact hosted mcptest callback URI.
  • Provider setup: Store the client ID and client secret only in operator-controlled server bindings.
  • Publisher evidence (reviewed 2026-08-24): https://docs.slack.dev/ai/slack-mcp-server/
  • Provider guidance: Browser OAuth requires the mcptest operator's SLACK_OAUTH_CLIENT_ID and SLACK_OAUTH_CLIENT_SECRET Worker bindings. Production readiness must not be claimed until both are configured.

VS Code MCP documentation

Latest validation evidence

Validation status
Online when last tested
Validation checked at
Aug 18, 2026 at 1:34 PM
Validation detail
Authentication challenge at https://mcp.slack.com/mcp returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication oauth