Civitai marketplace bridge. Search models/LoRAs publicly; download into comfyops model folders with dry-run + human outbox gate. Complements comfyops-mcp — do not run Comfy graphs here.
civitai-mcp has severe definition quality issues. The primary tool, civitai_models_tool, is a problematic 'portmanteau' combining 8+ distinct operations (search, get, download, pin_comfyops, outbox_enqueue, outbox_approve, outbox_publish, list_local) into a single tool with an overloaded 'operation' string parameter. This violates the single-responsibility principle and forces LLMs to guess which operation to invoke. Parameter descriptions are present but generic. The three helper tools (civitai_help, civitai_shutdown, show_depot_card) are minimal stubs. No output schemas are documented. Error handling is absent from visible code.
Help for civitai-mcp.
Portmanteau: search/get/download/pin_comfyops/outbox_* for Civitai → comfyops depot.
Signal graceful shutdown (process exit left to host).
Prefab card: local depot file count + pending download outbox.
civitai_models_tool violates single-responsibility principle: combines 8+ operations (search, get, download, pin_comfyops, outbox_enqueue/approve/publish, list_local) into one tool with a free-form 'operation' string parameter. LLMs cannot infer which operation to invoke without trial-and-error.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., model_id, version_id for chaining). Responses are unstructured.
civitai_models_tool parameter 'operation' is a free-form string with no enum constraint. Should enumerate valid operations: [search, get, download, pin_comfyops, outbox_enqueue, outbox_approve, outbox_publish, list_local]. Invites hallucinated invalid operations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
No error handling guidance visible. Tools do not indicate what to do on failure (retry, ask user, fatal). No recovery paths documented.
civitai_shutdown is marked IRREVERSIBLE but has no confirmation/dry-run mechanism. Agents can accidentally trigger graceful shutdown without safeguard.