docs: Slack MCP for factory agents (REV-1726) [auto-draft]

[rachaelrenk]

Auto-generated docs draft — REV-1726

This is an auto-generated first-pass docs draft created by the scan-new-specs workflow, which detected a newly merged spec with no corresponding docs coverage.

Feature: Self-hosted Slack MCP for Factory Agents (V0)
Spec: specs/REV-1726/PRODUCT.md in warp-server
Spec PR: https://github.com/warpdotdev/warp-server/pull/13221

New page: platform/factory-slack-mcp.mdx (proposed URL docs.warp.dev/platform/factory-slack-mcp).

Docs outline (auto-generated)

The following outline was generated from the spec. /cc @dagmfactory — please review and check off each item, or leave a comment with corrections.

Content structure

• H1: Slack MCP for factory agents
• Opening paragraph: Warp hosts a Slack MCP server that factory cloud agents consume automatically, giving them four Slack tools that act as the factory's own bot.
• Key features: automatic injection, factory bot identity, four tools, scope-aware tool list, no client changes
• How it works: automatic injection, credential-free sentinel resolution, per-factory identity/auth, run lifecycle
• Slack tools section: the four tools plus scope-to-tool mapping
• Errors, Security and auditing, Limitations
• Related pages: MCP servers, Slack integration, Software factory, Secrets

Items needing engineer verification ⚠️

• Feature flag self_hosted_slack_mcp — confirm the exact flag name and current rollout status (draft is marked V0 / behind a flag).
• Confirm the four tool names and parameter shapes are accurate and current.
• Confirm the short-lived token lifetime is 3 hours.
• Confirm the correct product name and casing for "factory" / "factory agents" in user-facing docs (terminology check).
• Confirm the proposed sidebar placement under Oz → Extending agents (see [TODO: docs reviewer — confirm placement] in sidebar.ts).
• Confirm whether this feature is ready to document publicly at all, or should stay internal until it ships.

Verified from spec ✅

• All content is drawn only from PRODUCT.md. No TECH.md-derived implementation internals were included (ambient-mode constraint).

Notes

• This spec has a TECH.md; per the ambient-mode drafting rules, no TECH.md content was used, since there was no engineer present to confirm what is safe to publish.
• The feature appears to be an early V0 behind a feature flag. A :::caution note flags this at the top of the page.

Conversation: https://app.warp.dev/conversation/d7900d79-cac7-4014-8e34-6c872853a77a
Run: https://oz.warp.dev/runs/019fa44e-0a22-7a77-bbb1-8181a25360fb

This PR was generated with Oz.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 27, 2026 4:10pm