AI & Emerging Interfaces

MCP Extension Connects Claude to Slack, Canva, and Figma

The Model Context Protocol now connects Claude to Slack, Canva, and Figma, letting the assistant act inside the tools where teams already work, The Verge reports.

  • AuthorSophie Lindqvist
  • ChannelAI & Emerging Interfaces
  • Filed
  • Read2 min
MCP extension unites Claude with apps like Slack, Canva, and Figma - The Verge
MCP extension unites Claude with apps like Slack, Canva, and Figma - The VergeMemoryCatcher / pixabay
  • The Verge reports an MCP extension connects Claude to Slack, Canva, and Figma
  • The Model Context Protocol is Anthropic's open standard for linking AI models to external applications
  • The integrations span messaging (Slack), visual design (Canva), and interface design (Figma)
  • The protocol standardizes connections, so each new app requires no bespoke model-side plumbing

The Model Context Protocol, Anthropic's open standard for connecting AI models to external tools, now links Claude to a set of widely used applications including Slack, Canva, and Figma, The Verge reports. The extension moves Claude from a chat window into the software where teams already hold their conversations, store their assets, and build their interfaces.

The report names three specific integrations: Slack for workplace messaging, Canva for visual design, and Figma for interface and prototype work. Each connection targets a distinct point in a product workflow — communication, graphic production, and design system work — rather than a single vertical.

What does MCP actually change for practitioners?

The Model Context Protocol defines a standard way for an AI model to request and act on data held in other applications. For a designer or product team, the practical consequence is straightforward: a request placed to Claude can now read from and write into the tools where the work already lives, instead of requiring the user to copy context back and forth by hand.

A designer working in Figma, for example, no longer needs to export a frame, paste it into a separate assistant, and carry the answer back. The connection runs through the protocol, so the exchange happens inside the existing workspace. The same applies to a team's Slack channels and to Canva projects.

This pattern matters for interface work in particular. Cross-application access removes the most error-prone step in AI-assisted workflows — the manual transfer of context between tools, where formatting is lost and versions diverge.

Why does the protocol approach matter?

MCP is a protocol rather than a set of one-off integrations. That distinction shapes what practitioners can expect: any application that implements the standard can expose its data and actions to a model, and the model side needs no bespoke plumbing for each new connection.

For teams that already rely on Claude, the reported extension reduces the number of separate tools and handoffs in a typical task. For teams evaluating AI assistants, it consolidates several integration decisions into one question: does the tool support the protocol?

The Verge's report centers on the named applications — Slack, Canva, and Figma — as the concrete beneficiaries of this extension.

What comes next?

If adoption of the protocol continues across mainstream design and communication tools, the boundary between the assistant and the working file becomes a configuration choice rather than a hard limit.

Source: Google News: Figma update

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

Staff writer covering people, launches and day-to-day practice in Product and interaction design, design systems at Interface Wire.

64 articles

Related articles

  1. Anthropic Brings Interactive MCP Apps to Claude Surfaces

  2. Claude Code Figma MCP Closes the Loop With Two-Way Sync

  3. Figma Adds 20 MCP Partners Including Sarvam in Expanded AI Push

  4. Figma Opens Its Design Tools to AI Agents

« Previous articleNext article »