Open implementations · local creative tools

One protocol. Different creative worlds.

Creative MCP brings together independent implementations for the creative applications you already use. Each project has its own setup, requirements and capabilities.

Adobe MCP

Local MCP servers for InDesign, Illustrator, Photoshop, After Effects and Premiere Pro, with a coordinator for two documented cross-app workflows.

Five application-specific implementations
One suite coordinator for two documented cross-app workflows
Node.js 18+, macOS or Windows
Install with brew install zachshallbetter/tap/adobe-mcp or npx

Explore Adobe MCP →

Blender MCP

A Rust MCP server and companion Blender add-on for scenes, objects, materials and 3D asset pipelines.

Stdio MCP server with local Blender IPC
Blender 4.0+ and the companion add-on
Install with brew install zachshallbetter/tap/blender-mcp or Cargo from source

Explore Blender MCP →

These projects are separate MCP implementations. They can be configured in a compatible client at the same time, but direct Adobe-to-Blender orchestration is not currently part of either project.

Adobe MCP · five creative surfaces

Choose a place to start.

Each Adobe server has its own tools and workflow. Read the implementation guide for app-specific requirements and behavior.

Browse Adobe application implementations → · Explore the Capability Atlas →

An open collection

More creative tools can join as they’re ready.

New projects will be added as their implementations, documentation and evidence are ready to share. Explore workflows across the current projects →

Ready to try it?

On a Mac, one installer finds your creative apps and MCP clients, shows its plan, then installs, registers and checks every server.

brew tap zachshallbetter/tap
brew trust zachshallbetter/tap
brew install zachshallbetter/tap/creative-mcp
creative-mcp setup

Every setup option →What the installer does →