Anthropic releases 9 Claude connectors for Blender, Adobe, and creative software via MCP protocol
Anthropic has released nine connectors that integrate Claude with creative tools including Blender, Adobe Creative Cloud, Ableton, and Autodesk. The connectors use Anthropic's Model Context Protocol (MCP), allowing Claude to interface directly with creative software workflows.
Anthropic releases 9 Claude connectors for Blender, Adobe, and creative software via MCP protocol
Anthropic has released nine connectors that integrate Claude with creative tools including Blender, Adobe Creative Cloud, Ableton, and Autodesk. The connectors use Anthropic's Model Context Protocol (MCP), allowing Claude to interface directly with creative software workflows.
The nine connectors
The full list of creative tool integrations:
- Ableton: Grounds Claude's answers in official documentation for Live and Push
- Adobe: Enables control of 50+ Creative Cloud tools including Photoshop, Premiere, and Express
- Affinity by Canva: Automates batch image adjustments, layer renaming, and file exports
- Autodesk Fusion: Creates and modifies 3D models through conversations for Fusion subscribers
- Blender: Provides natural-language interface to Blender's Python API
- Resolume Arena and Wire: Controls visual performance software in real time via natural language
- SketchUp: Converts conversations into 3D model starting points
- Splice: Searches catalog of royalty-free music samples from within Claude
Blender integration details
The Blender connector, built by Blender developers using MCP, allows 3D artists to analyze and debug entire scenes, build custom scripts to batch-apply changes to objects, and add new tools directly to Blender's interface using its Python API.
Anthropic has become a Blender Development Fund patron. The company notes that because Blender's connector uses MCP, other large language models can also connect to Blender.
What this means
This release represents Anthropic's first major push into vertical-specific integrations for creative professionals. The MCP protocol approach is strategic: by building connectors as open tools rather than proprietary integrations, Anthropic enables other AI models to use the same infrastructure while positioning Claude as the default choice for creative workflows. The Blender partnership is particularly notable—supporting an open-source project while gaining a connector that works with any LLM demonstrates a community-first approach that could accelerate MCP adoption across the creative tools ecosystem.
Related Articles
Anthropic reverses course on invisible Claude Fable distillation guardrails after researcher backlash
Anthropic is making its anti-distillation safeguards visible in Claude Fable 5 after backlash over silently degrading responses when it detected attempts to use the model for training competing systems. Queries suspected of distillation will now be routed to Claude Opus 4.8 with explicit user notification, matching how the company handles other high-risk areas.
Anthropic reverses stealth policy that secretly downgraded Claude Fable 5 for AI research tasks
Anthropic is making visible its policy of restricting Claude Fable 5 for certain AI development tasks, after researchers discovered the model was secretly rerouting requests to lesser models without disclosure. The company apologized for the lack of transparency but maintained the underlying restrictions.
Anthropic Reverses Policy That Silently Throttled AI Researchers Using Claude
Anthropic has reversed a controversial policy that would have made Claude Fable and Mythos models silently throttle responses to researchers working on frontier AI development. The policy, disclosed in the system card, would have identified and limited effectiveness of requests targeting LLM development without notifying users.
Microsoft restricts Claude Fable 5 internally over 30-day data retention requirement
Microsoft has restricted internal employee access to Anthropic's newly released Claude Fable 5 model while its legal teams evaluate the company's new data retention requirements. The model requires storing prompts and outputs for 30 days to operate safety classifiers, with some content potentially retained for up to two years if flagged for policy violations.
Comments
Loading...