What happened
- On September 2, 2026, Adobe announced the Adobe for Slack app, which exposes more than 70 tools from its programs inside Slack.
- The catalog includes Firefly, Adobe Express, Photoshop, Premiere, Acrobat, InDesign, Illustrator, Stock and Lightroom.
- The integration runs on Slackbot: someone describes what they need in natural language and the assistant calls the right tool, pulling context from messages, files, channels and Canvases in the workspace itself.
- It is available globally to teams on Slack Business+ and Enterprise+ plans, on desktop, web and mobile. It can be used without an Adobe account; signing in unlocks more features and access to Creative Cloud files.
Why it matters
- The move isn’t about product, it’s about location. Adobe stops competing for the open tab and becomes a service an agent calls from wherever the conversation already is. Whoever directs the work is no longer the designer but the thread.
- The protocol that makes it possible, MCP, is open. Any software vendor that publishes an endpoint can do the same, and Canva and Figma already did when Slack added support in June. So did OpenAI, with a work mode that connects private data to external content.
- The consequence the announcement doesn’t mention: when generation happens inside the chat, the draft and the approved piece end up in the same place and look the same. Version control stops being a folder and becomes a conversation, which is a worse archive.
The number
70 tools. The same number Adobe already exposes in its ChatGPT connector. The implementation is practically identical across both platforms.
Context
Slack added MCP support to its assistant in June 2026, with Canva and Figma as the first integrations. Adobe already had connectors for ChatGPT, Claude and Copilot, and has announced one for Gemini. Slack’s head of product, Jaime DeLanghe, presented the case as proof that MCP apps turn conversation into action. The division of labor was explicit: Salesforce provided the routing, Adobe the tools and the gateway into Creative Cloud.
What’s next
- The Gemini integration was announced without a date.
- No timeline has been announced for extending the app to Slack plans other than Business+ and Enterprise+.
- It remains an open question whether the C2PA provenance credentials Adobe attaches when generating survive the cycle of downloading and re-uploading inside the chat. An intermediate save can wipe the manifest.
Bottom line
Adobe attaches provenance credentials to what it generates, and Anthropic has just published a verifier for its own. Moving production into the chat tests exactly that: whether the trail makes it to the final file or gets lost along the way.
