/ /

Slack MCP Snap-in

DevRev's Slack snap-in registers Slack's remote MCP server in DevRev, allowing agents and users to search, read, send, and manage Slack workspace content through DevRev.

Installation

A DevRev admin installs the snap-in once. The organization Slack connection enables /askdr automations in Slack, and is required before the snap-in can be installed.

  1. In DevRev App, go to Settings, then Snap-ins, search for Slack MCP Snap in, and open it.

  2. Choose Install.

  3. Under Organization Settings, add the organization Slack connection once (Add connection, then Connect).

  4. Under Configuration, select a default part for /askdr create-ticket and /askdr create-issue.

  5. Choose Install Snap-in.

User setup

Each user connects Slack Remote so Computer can call the Slack MCP server. This is separate from the organization connection used for /askdr automations.

  1. In Computer, go to Settings, then Connectors, and open Slack MCP Snap in.

  2. Choose Connect, then Allow the Computer by DevRev app in Slack.

  3. After setup, use Computer to search, read, and send Slack content. Use /askdr in Slack for DevRev automations.

Server name

Slack MCP

Slug

slack-mcp

Server type

Remote

MCP URL

https://mcp.slack.com/mcp

Auth

OAuth 2.0

Scopes

See OAuth Scopes

Note: This integration operates on-demand over Slack's hosted MCP server. It is not a bulk migration or continuous two-way sync of DevRev work items like traditional AirSync systems.

Key capabilities

Slack's hosted MCP server exposes tools for searching, reading, sending, and managing messages, channels, canvases, files, and users. The exact capabilities available to a session depend on the connected user's Slack plan, workspace permissions, and admin approvals.

Permissions and access

  • User OAuth required — Each user must complete the OAuth consent flow to connect their Slack account. The MCP server does not support headless or service-account authentication.

  • Workspace admin approval required — A workspace admin must approve the MCP integration before any user in the workspace can connect. See App Management.

  • Workspace permissions apply — Tools can only access content the connected user can already see in Slack. Private channels, DMs, and files the user cannot access in Slack are equally inaccessible via MCP.

  • Write access — Agents can send messages, create conversations, add reactions, and schedule messages. Review agent actions carefully before execution.

Plan-based access

  • Message history — On Free plan workspaces, SlackReadChannel and SlackReadThread are limited to the last 90 days of message history. Pro and above have full history.

  • All other tools — Available across all Slack plans with no explicit plan gate.

See Slack pricing and plan features for full details.

Attachments

Only text-based file content can be read and displayed directly. Binary file types such as images, PDFs, and other non-text formats are not decoded. For those files, you can view or download them directly from the Slack interface if needed.

Rate limits

  • Subject to Slack rate limiting

  • Requires retry/backoff for high-volume usage

Transport

  • Primary: Streamable HTTP at https://mcp.slack.com/mcp

  • SSE transport: Not supported

  • Dynamic Client Registration: Not supported

  • Auth: OAuth 2.0 (Confidential) — uses client_id and client_secret; refresh tokens supported. See OAuth discovery endpoints.

Privacy

You can find more about DevRev's privacy policy at https://devrev.ai/privacy-policy/

Was this article helpful?