danielgwilson Image MCP
Use the image-mcp CLI for Image MCP workflows.
If image-mcp is not installed globally, use npx --yes @image-mcp/cli ... instead. If npx fails because of local npm cache permissions, retry with NPM_CONFIG_CACHE="$(mktemp -d)" npx --yes @image-mcp/cli ....
Use this skill when
- the user wants to create an image with Image MCP
- the user wants to edit or remix an image with Image MCP
- the user wants to upload a local image for later editing
- the user wants to inspect Image MCP generation history
- the user wants to inspect Image MCP model capabilities
Do not use this skill when
- the user only wants generic image analysis
- the user wants a different image provider specifically
- the task is not actually about Image MCP
Workflow
- If
image-mcpis onPATH, use it directly. Otherwise usenpx --yes @image-mcp/cli ...or install it globally withnpm install -g @image-mcp/cli. - Run
image-mcp doctororimage-mcp whoamiif auth state is unclear. - If auth is missing or stale, run
image-mcp loginand thenimage-mcp whoami. - Use
image-mcp models --jsonwhen you need current model capability info. - Prefer
--jsonwhen another agent step will consume the result. - Use
image-mcp create "<prompt>"for generation tasks. It waits by default; use--asyncwhen you want a job id immediately. - Use
image-mcp edit <image-ref> "<prompt>"for edits. Local file paths are uploaded automatically before the edit job is created. - Use
image-mcp job listto recover long or interrupted runs andimage-mcp job get <job-id>to inspect a specific job. - Use
image-mcp job wait <job-id> --jsonwhen you need explicit polling instead of the default wait behavior. - Use
image-mcp job cancel <job-id>when a queued or running job should be stopped.
Fast path
image-mcp loginimage-mcp whoamiimage-mcp create "<prompt>"npx --yes @image-mcp/cli login
References
- For command usage patterns, see references/cli-usage.md
- For model selection guidance, see references/model-selection.md
- For troubleshooting, see references/troubleshooting.md