Find, evaluate, and shortlist creators with AI

Help me install and configure hiCreator Agent in this AI client:

1. Identify this client, OS and execution environment (macOS, Windows PowerShell/CMD or WSL). Configure only the environment where this client runs. Ask if uncertain; do not guess configuration paths. Preserve existing servers and settings; inspect an existing hiCreator entry before updating it, avoiding duplicates.

2. Let me enter the API key in the client's credential UI or my own local interactive terminal. Never ask for it in chat, put it in command arguments, print or log it, or expose it while inspecting existing settings. If secure input is unavailable, give me the exact manual steps and continue after I complete them.

3. For Codex, Claude Code or Cursor, when that environment has Node.js 20+, npm and a terminal supporting secure user input, run npx --yes --prefer-online hicreator-agent@latest setup --clients CLIENT, replacing CLIENT with codex, claude or cursor respectively. Use npx.cmd on native Windows and npx on macOS/WSL. Do not change PowerShell execution policy or configure a Windows client inside WSL. If the command is unavailable or setup fails, explain why and use manual configuration instead of repeatedly retrying or installing another client.

4. For other clients, including WorkBuddy, or if these prerequisites are unavailable, follow the client's current official instructions to configure remote Streamable HTTP MCP: URL https://mcp.hicreator.ai/mcp; Authorization: Bearer <HICREATOR_API_KEY> (placeholder only).

5. If this client supports Agent Skills, check for the hicreator Skill; setup already installs it. If missing, use the client's official method to install skills/hicreator from https://github.com/Archivev/hicreator-agent. For manual installations or environments without npm, use the installed Skill directly; prepare is not a prerequisite.

6. Verify with MCP initialization and tools/list, checking tool names against the repository’s current Skill and reporting the actual count instead of requiring a fixed count. Do not call business tools for testing. Confirm this client has loaded the tools and Skill where supported; explain any reload or new session needed. Report configuration, verification and remaining steps separately. Writing configuration alone does not prove success.