LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Slack Workspace

Slack's own endpoint — search, messages, canvases and user management, scoped by app permissions.

by Slack ↗Team Chat Platforms✓ Official

These plugins include connection settings for this server:

LABSCO SUMMARY

The confidential-client requirement is the point, not an obstacle.

Slack holds most organisations' entire informal record, and a public client — one where the credential lives on the user's machine — would make that reachable by anything the user installs. Requiring a registered app with a secret puts the connection under the workspace's existing app approval process, where an admin can see it and revoke it. That is why the URL works only in the partner-built clients Slack lists — Claude.ai, Claude Code, Perplexity and Cursor — or through an app your workspace registers, and why you should be suspicious of any other client claiming it can connect. Per-tool scopes are the second half: read without write is expressible here.

What it is

Slack's official endpoint, spoken over streamable HTTP. Not every client can point at it: the connection has to come from a registered Slack app — one of the partner-built clients Slack lists (Claude.ai, Claude Code, Perplexity, Cursor), or an app your workspace registers.

What you get

  • Search — messages, files, users, channels and emoji
  • Messages — send, draft, read history, work in threads, create conversations, add reactions
  • Canvas — create, update and read
  • User management — profiles and channel membership

Requirements

  • A confidential OAuth client, meaning a Slack app with a client ID and secret — directory-published or internal only
  • Scopes are per tool, so an app can hold search access without the ability to post
  • As an end user you connect through a partner app; your workspace admin approves it like any other Slack app

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen

See installation options