Slack (Official)

Hosted by a third party. This MCP server is built and hosted by the vendor, not Runlayer. This guide covers connecting it through Runlayer for governance, policies, and audit.

Connect agents to Slack through Slack’s official MCP server, hosted by Slack at mcp.slack.com. Once connected, an agent can read and send messages, follow threads and channel history, search the workspace, work with Canvases, and look up users. Each connection belongs to the person who authorizes it, and connector actions use that person’s Slack identity and permissions. Runlayer adds identity-aware policy, runtime scanning, and an audit trail around this access. Admins decide what each agent can reach and who can use it.

Available Tools

Tool	Description
`slack_send_message`	Send messages to channels or users
`slack_schedule_message`	Schedule messages for future delivery
`slack_create_canvas`	Create Slack Canvas documents
`slack_read_canvas`	Read Canvas document content
`slack_search_public`	Search messages/files in public channels
`slack_search_public_and_private`	Search all channels including private/DMs
`slack_search_channels`	Find channels by name or description
`slack_search_users`	Find users by name, email, or profile
`slack_read_channel`	Read messages from a channel
`slack_read_thread`	Read messages from a thread
`slack_read_user_profile`	Get user profile information
`slack_send_message_draft`	Create draft messages

Setup

Runlayer-managed connector OAuth (Recommended)

Runlayer-hosted deployments can use Runlayer’s Slack Marketplace app to authorize this connector. You don’t need to create a Slack app or provide client credentials.

Add the connector

In Runlayer, go to Connectors > Add connector, choose Slack, and click Create.

Authorize your Slack account

On the connector page, click Connect, select your workspace, and click Allow.

Runlayer’s Marketplace app requests connector permissions and permissions to create and manage dedicated Slack apps for agents in one authorization. Connector access, Slack notifications, and dedicated agent apps remain separately enabled capabilities; Runlayer uses each permission only when its corresponding capability is enabled and allowed by policy. See Slack integrations for the workspace-level setup.

Bring your own Slack app

If your organization prefers its own internal Slack app, configure the connector as a Pre-registered Client.

Create Slack App from Manifest

Go to Slack API: Applications
Click Create New App > From a manifest
Select your workspace and click Next
Paste this manifest, replacing <your-runlayer-host> with your deployment’s host:

display_information:
  name: Runlayer Slack MCP
  description: Official Slack MCP via Runlayer
  background_color: "#2c2d30"
features:
  bot_user:
    display_name: Slack MCP
    always_online: false
oauth_config:
  redirect_urls:
    - https://<your-runlayer-host>/oauth/callback
  scopes:
    user:
      - search:read.public
      - search:read.private
      - search:read.mpim
      - search:read.im
      - search:read.files
      - search:read.users
      - chat:write
      - channels:history
      - groups:history
      - mpim:history
      - im:history
      - canvases:read
      - canvases:write
      - users:read
      - users:read.email
      - reactions:write
      - reactions:read
      - emoji:read
      - files:read
      - channels:write
      - groups:write
      - im:write
      - mpim:write
      - channels:read
      - groups:read
      - mpim:read
    bot:
      - commands
settings:
  org_deploy_enabled: true
  socket_mode_enabled: false
  token_rotation_enabled: false

The bot user and commands scope are required by Slack for org-wide installs but are unused by Runlayer.

Click Next, review the summary, then click Create

Enable MCP

In your app settings, go to Agents & AI Apps in the sidebar
Enable MCP Server for your app

Install App to Workspace

Go to Settings > Install App in the sidebar
Click Install to Workspace/Organization and authorize the app

Get Credentials

Go to Basic Information in the app settings
Copy the Client ID and Client Secret

Add the connector in Runlayer

In Runlayer, go to Connectors > Add connector and choose Slack
Under Show advanced settings, set Registration to Pre-registered Client
Enter the Client ID and Client Secret
Click Create

Authorize

Click Connect on the connector page
Select your workspace and click Allow

After you connect

Attach the Slack connector to any AI assistant or agent in Runlayer. It can then summarize threads, draft and send messages, search across channels, and work with Canvases within the policies you set. To give an agent its own Slack identity for mentions and DMs, a workspace admin must separately configure dedicated Slack apps. Manage access, permissions, and audit logs under Connectors > Slack.

Privacy

Runlayer’s handling of your data is described in our Privacy Policy.

Troubleshooting

MCP access not enabled

Runlayer’s managed Slack app is approved for MCP access. If you bring your own app, Slack requires it to be an internal app or published in the Slack Marketplace. Check Slack’s MCP documentation for current eligibility.

Redirect URI mismatch (bring-your-own-app)

Verify your Slack app’s redirect URL is exactly https://<your-runlayer-host>/oauth/callback with no trailing slash.

Missing scopes error

Ensure all scopes from the manifest are added to your Slack app. The official MCP server requires specific scopes that differ from the standard Slack API scopes.

Enable

Control

Self-Hosted Deployment

Operations

Cookbook

Integrations

Connectors

Resources

Available Tools

Setup

Runlayer-managed connector OAuth (Recommended)

Bring your own Slack app

After you connect

Privacy

Troubleshooting

​Available Tools

​Setup

​Runlayer-managed connector OAuth (Recommended)

​Bring your own Slack app

​After you connect

​Privacy

​Troubleshooting

Available Tools

Setup

Runlayer-managed connector OAuth (Recommended)

Bring your own Slack app

After you connect

Privacy

Troubleshooting