Choose a tool
Pick an implementation, such as Adobe MCP or Blender MCP.
Local MCP servers connect your creative applications to agent workflows, so your tools, files and context can work together.
Creative MCP hosts independent, open implementations that connect creative tools to agent workflows.
Connect your Adobe creative apps.
AvailableFive app-specific MCP servers, with a coordinator for supported cross-app workflows.
Explore Adobe MCP ↗Work with 3D scenes, objects, materials and animation.
AvailableA Rust MCP server and Blender companion add-on for scene tools, assets and pipelines.
Explore Blender MCP ↗Creative MCP is an open platform; implementations are developed and released independently.
A simple local setup connects your creative applications to your chosen agent workflow.
Pick an implementation, such as Adobe MCP or Blender MCP.
Install and configure the local server and any app companion it needs.
Your tools stay open on your machine. Work with your files and context where supported.
Give agents a way to work with your actual creative tools, files and context. Each implementation runs locally and documents its own setup.
brew tap zachshallbetter/tap
brew trust zachshallbetter/tap
brew install zachshallbetter/tap/creative-mcp
creative-mcp setupbrew tap zachshallbetter/tap
brew trust zachshallbetter/tap
brew install zachshallbetter/tap/adobe-mcpbrew tap zachshallbetter/tap
brew trust zachshallbetter/tap
brew install zachshallbetter/tap/blender-mcpclaude mcp add --scope user adobe -- npx -y adobe-mcp-suitecargo install --locked --git https://github.com/zachshallbetter/blender-mcp-rs --package blender-mcp-cliEach implementation provides transparent information about its current capabilities, so you know what to expect.
Guides explain what the implementation does and how to set it up.
The tools and capabilities are present in the MCP server.
Automated checks cover the tool implementation where provided.
Live-app validation is reported separately and depends on the implementation.
Adobe MCP’s Capability Atlas tracks evidence by feature. For Blender MCP, see the project’s current repository documentation. A tool passing automated checks does not by itself prove that a workflow has been validated in a live application.
Move approved artwork and its context into Blender, then keep building in the tools you already use.
Shape a layout and approve the artwork in InDesign.
Export the approved assets and carry the brief into the next tool.
Bring those assets into Blender and continue building in 3D.