Civitai Account Status

This is the node you run once, right after installing the pack, to find out whether your API key actually works - and which account it belongs to - before you point anything that posts at it. It takes zero inputs and hands back five facts about whoever owns the key.

The pack talks to Civitai's own MCP server (https://mcp.civitai.com/mcp) using JSON-RPC over HTTP, and this node is a thin wrapper around its whoami tool. Give it a key, it sends an Authorization: Bearer header, and Civitai answers with the account behind that key. No key, no output: the node just raises a helpful error telling you exactly where to put one.

What you actually get

Five outputs, all of which are meant to be read, not wired into a sampler:

• username (STRING) - your Civitai handle.
• user_id (INT) - your numeric user ID.
• is_moderator (BOOLEAN) - true if the account is a staff moderator.
• is_onboarded (BOOLEAN) - true if the account has completed signup onboarding.
• muted (BOOLEAN) - true if the account is muted/restricted.

Since it's an output node, you can drop it at the end of a graph and wire the strings into a text-display node (the kind every workflow already has) to see them on screen. That's the whole job. The genuinely useful case: if you keep multiple Civitai accounts - a common setup after the 2025–2026 policy churn pushed a lot of creators toward alt accounts - this is the fast, unambiguous check that the key ComfyUI is using belongs to the account you think it does.

Installing it and setting the key

Same drill as every node in this pack. In ComfyUI Manager, search ComfyUI Civitai MCP and install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/daceheg/ComfyUI-civitai-mcp.git

Restart ComfyUI after. The pack's only real dependency is requests; PIL, numpy and torch come from ComfyUI itself, so there's no separate environment to fight.

The key is deliberately not a node input. ComfyUI bakes your workflow - including literal widget values - into saved PNGs by default, so a text field on the node would leak your key into every image you post. Instead, create a file named civitai_key.txt inside the pack folder (ComfyUI/custom_nodes/ComfyUI-civitai-mcp/civitai_key.txt) containing only your key, or set a CIVITAI_API_KEY environment variable. Grab a key at civitai.com/user/account.

Where people get burned

Missing key: the node throws a ValueError that spells out the exact path to create. Fix that and restart. Wrong key: Civitai answers the whoami call with a 401, and the node surfaces the error message. And if muted comes back true - that's your account telling you it's already in Civitai's bad books. Given that Civitai now runs VLM-based auto-moderation and hands out mutes and bans at scale, treat that flag as "read the Terms of Service before you post anything automated." This is also a young pack (v1.4.0, first released mid-2026, tiny user base), so the failure modes you'll hit are Civitai's, not the author's - and this node is the cheapest way to find out which side of that boundary you're on.