civitai

# Civitai + comfyui-mcp Civitai ships an **official remote MCP server** — discovery and the whole community surface — and comfyui-mcp owns the **local machine**: download, wire, queue, tag. They compose. comfyui-mcp deliberately does **not** proxy or re-expose Civitai's tools; MCP clients connect to both servers at once, so the right pattern is *pairing*, not wrapping. ## Is the Civitai MCP connected? Look for `mcp__civitai__*` tools in your session (e.g. `mcp__civitai__search_models`). **The `comfy` plugin bundles it** — its `.mcp.json` declares the Civitai remote server alongside comfyui, so plugin users get `mcp__civitai__*` automatically with **no manual setup and no key required** (the `Authorization` header defaults to an empty Bearer, which Civitai accepts for its read/browse tools). It just works headless. - **Present** → use it for discovery (this skill's main path). - **Absent** (standalone MCP install, not the plugin) → either install the plugin, or add the server once: ```bash claude mcp add --transport http civitai https://mcp.civitai.com/mcp \ --header "Authorization: Bearer YOUR_CIVITAI_API_KEY" ``` Until then, fall back to `search_models` (HuggingFace) + `download_civitai_model` by id/URL. **API key (optional).** Browsing/search needs none. To unlock the user's account context (favorites, posting, **gated/early-access downloads**), set `CIVITAI_API_TOKEN` (from civitai.com/user/account) in the environment — the **same** variable comfyui...