Supported agents
Each agent gets the same skill and the same tools, through its own supported mechanism.
Claude Code
A project skill in .claude/skills/elite-taste/ and a remote MCP server in .mcp.json. Claude loads the skill when you ask for design work. Global install instead:
npx elite-taste init --agent claude --global
claude mcp add --transport http --scope user elite-taste https://elite-taste.vercel.app/api/mcp \
--header "Authorization: Bearer ${ELITE_TASTE_API_KEY}"Cursor
A project rule in .cursor/rules/elite-taste.mdc (agent-requested, not always on) and the server in .cursor/mcp.json.
Codex
The skill becomes a marked block in AGENTS.md (re-running the installer replaces the block, never duplicates it). Codex connects to the hosted server over Streamable HTTP and reads the key from your environment:
[mcp_servers.elite-taste]
url = "https://elite-taste.vercel.app/api/mcp"
bearer_token_env_var = "ELITE_TASTE_API_KEY"Any other MCP client
Point it at https://elite-taste.vercel.app/api/mcp (Streamable HTTP) with Authorization: Bearer $ELITE_TASTE_API_KEY. Paste the skill text into the client's rules.