creativeclaw
Creative Claw
For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw/references/workflow-basics.md). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.
Not connected yet? If no Creative Claw tools (such as list_models or generate_image) are available, the plugin is installed but the server is not connected. Stop and give the user the click path: open the Creative Claw plugin page in Claude, then the Connectors tab, press Connect, press Add if an "Add custom connector" dialog opens, and sign in. In Claude Code they run /mcp instead. Then they ask again. Do not substitute other tools or describe a result that was not generated.
Read shared execution guidance once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.
Use the Creative Claw MCP server as a media workspace: source durable assets, apply a brand theme, choose a model by capability, generate or process media, and save results for reuse.
Account and billing questions
Use manage_account for the current balance and for recent generations with their recorded charges and refunds. Read account and cost guidance before interpreting charges. Use estimate_generation for future quotes, not the cost of a past generation. Do not submit feedback automatically for an account question.
Purchases and plans are handled on the Creative Claw website, not in chat. Do not start, price, or recommend a purchase; if asked, say so and share only an account link a tool returned.