01 · Records and state owned
Messages, message drafts, files, public and private channels, threads, users, profile fields, statuses, channel membership, custom emoji, reactions, conversations, and canvases.
Slack
Slack
Slack belongs in Atlas because it operates both a user-scoped MCP server for workspace actions and a Slackbot client that invokes approved tools from external servers.
Work & collaborationSystem of coordinationBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Search messages, files, users, channels, and emoji; read channel or thread history, canvases, user profiles, and conversation membership permitted to the user token.
03 · Actions and write paths
Send or draft messages, create channels or direct-message conversations, add reactions, and create or update canvases on behalf of the authenticated user.
04 · Authentication and permissions
Slack's hosted server uses confidential OAuth user tokens and tool-specific Slack scopes through a fixed registered app; Slackbot connections separately support no-auth, Slack identity, DCR, or manual OAuth.
05 · Monitoring, approval, and recovery
Admins manage provider apps through Slack approval and audit controls. Slackbot requires explicit authorization for each third-party tool call, with allow-once, always-allow, and deny choices.
06 · Limits and caveats
The provider supports Streamable HTTP but not SSE or dynamic client registration, only Marketplace or internal apps may connect, and Web API rate limits apply per tool.
Agent access
MCP support
Official MCP server + 3rd Party MCP servicesSlack-hosted MCP Server plus separate Slackbot MCP ClientCurrent documented service; not supported in GovSlack
Support: Official MCP server + 3rd Party MCP services
Read scope: Search workspace messages, files, people, channels, and emoji; read histories, threads, canvases, profiles, and members within the installed app's user scopes and conversation access.
Write scope: Draft or send messages, create public or private conversations, add reactions, and create or update canvases as the authenticated Slack user.
Authentication: The hosted provider uses confidential Slack OAuth through a fixed app ID; Slackbot can authenticate external servers through Slack identity, DCR, manual OAuth, or no authentication.
Approval boundary: Preview message content, audience, channel visibility, and canvas changes before provider writes; treat Slackbot's persistent always-allow choice as a separate user authorization requiring clear revocation.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Slack ships them.
Single-platform patterns
- Agent supervision, campaign coordination, and alert inbox
- Marketing launch room
- Agent supervision inbox
- Cross-functional approval workspace
Multi-platform compositions
- Slack + campaign or CRM system: marketing launch room
- Slack + content-production platform + analytics or automation system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
MCP / agent-role validationRepresentative source
https://docs.slack.dev/ai/slack-mcp-server/ ↗Provider tools, OAuth scopes, fixed app identity, admin controls, transport and rate limits; Slackbot auth methods and per-tool consent
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Slack provider tools, OAuth, app controls, and Slackbot client role reviewed 2026-07-22
APISource inventory
https://api.slack.com/methods ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://api.slack.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://slack.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCPSource inventory
https://api.slack.com/docs/apps/ai ↗First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://api.slack.com/apis/connections/events-api ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.