Make a useful tool easier to reach.
Creative MCP is a collection of open implementations for creative applications. A contribution should make one implementation or a documented workflow more useful while keeping its capabilities and limits clear.
Choose the right home for the change.
Adobe MCP
Adobe app servers and coordinator work live in the Adobe MCP repository. Follow that repository’s contributor instructions and app-specific requirements.
Open Adobe MCP on GitHub ↗Blender MCP
The Rust CLI, Blender companion add-on and Blender-specific documentation live in the Blender MCP repository. Follow its current build and contribution guidance.
Open Blender MCP on GitHub ↗Join the series with the same conventions.
A new implementation gets its own repository, published package, Homebrew formula in zachshallbetter/tap, implementation guide and, a catalogue entry with detection rules checked on a real machine. Names follow one pattern: <id>-mcp for the repository, formula and package, and <id>-mcp-<app> for per-app servers.
Site, docs and catalogue changes go to the public creative-mcp repository; see its contribution guide.
Show what changed and how you know.
State the user task.
Name the application, the operation, the required input and the expected result. Keep the change scoped to the relevant implementation.
Keep claims tied to evidence.
Distinguish documented, implemented, automated-check tested and validated in the real application. Link the source or run record behind each claim.
Document setup and limits.
Record supported application and client versions, permissions, platform differences, failure cases and any manual handoff still required.
Describe the handoff honestly.
When an example spans implementations, list which server performs each step, what the person exports or imports, what the client coordinates, and which operations have actually been validated. Do not imply automatic file transfer or cross-server orchestration unless the code provides it.