Slack

Active

An AI agent for Slack. It works in a scene with a live connection to Slack. It asks before it writes, and every run is traced.

Read and post messages in Slack channels, search message history, reply to threads, add reactions, and write canvases — the documents that live inside Slack. Connect your Slack workspace to keep AI in sync with team conversations.

Communication OAuth 3 asset types 8 tools

What you can connect

Add these to your scene and AI gets access.

Account Accounts

A connected Slack workspace

WorkspaceTeam IDBot User

Channel Channels

A Slack channel for team communication

NameTopicMembersPrivate

Guide Guides

Slack setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.

TitleSummary

Tools

What the agent can do once this is connected.

Writes 8

Change data in the connected system.

slack_list_channels List channels in the Slack workspace.

slack_get_channel_info Get detailed information about a Slack channel.

slack_read_messages Read recent messages from a Slack channel.

slack_read_thread Read all replies in a Slack thread.

slack_search_messages Search for messages across Slack channels.

slack_post_message Post a message to a Slack channel.

slack_reply_to_thread Reply to a Slack thread.

slack_add_reaction Add an emoji reaction to a message.

Connect Slack over MCP

Daslab is itself an MCP server.

Connect Slack in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Slack tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Slack and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Search and summarize channel discussions
Post status updates to team channels
Monitor channels for specific topics or keywords
Keep a channel canvas up to date as a living runbook

Knowledge base

Writing Slack canvases canvases
Standalone vs channel canvases, the canvases:* scopes and who can see a new canvas, why canvas bodies take markdown and not mrkdwn, and the section-lookup → edit loop.

Ships with the integration — agents read these with docs_read, before the account is connected. Knowledge bases →