# Recraft — Recraft joins the MCP ecosystem (and why it matters)

- Company: Recraft (recraft.ai)
- Announced: 2025-07-14
- Category: not stated
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://www.recraft.ai/blog/recraft-mcp
- Record: https://forck.live/items/23963-recraft-joins-the-mcp-ecosystem-and-why-it-matters
- Subject: Recraft V4

Recraft now supports the Model Context Protocol, letting you generate images directly through Claude, Cursor, and other AI agents without switching between tools. When AI models operate in the wild beyond chat windows and playgrounds, the question isn't "Can the model generate something?" It's "Can the model work within a real system?" This is where context becomes everything: tools, data, user intent, and workflow logic. Historically, integrating those pieces has been clunky — messy snippets of prompt hacks, hand-coded APIs, or manual copy-paste workarounds. The approach doesn't scale. It doesn't generalize. And it certainly doesn't enable the kind of modular, intelligent behavior that creative workflows demand. That's why Recraft is now live with MCP (Model Context Protocol), an open standard designed to make tools like ours deeply accessible to the next generation of AI agents and chat interfaces. What is MCP? At a technical level, MCP defines a standardized interface for exposing three key things to AI models: Tools (actions the model can take, like running an image generation) Resources (contextual data like files, styles, or palettes) …

---

Record: https://forck.live/items/23963-recraft-joins-the-mcp-ecosystem-and-why-it-matters
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md