Skip to main content
Bring brand extraction into your AI coding agent. Instead of calling the HTTP API yourself, your agent can extract a website’s design system, read it back, and build on-brand pages directly inside tools like Claude Code, Cursor, Codex or any other MCP client. There are two pieces, and they work best together:

MCP server

The tools. Connect the Taste Engine MCP server so your agent can submit a URL, poll status, read the extracted brand system, and search the corpus for a look.

Skills

The know-how. Install the agent skills that find real design references before building, ship new pages inside an existing brand’s identity, and verify them against it.

​
Which one do I need?

  • The MCP server gives your agent the tools to call the engine. It is the part that does the work.
  • The skills are sets of instructions that teach your agent how to use those tools well: search for the look the prompt actually describes and inspect every result, read every section of the extraction, follow the captured screenshot, and compose the result as real design rather than a generic template.
The skills call the MCP tools, so for the full experience you install the skills and connect the MCP server. You can also connect the MCP server on its own and prompt your agent directly.

​
Prerequisites

  • A taste_ API key. Create one in the Engine dashboard. The same key authenticates the HTTP API and the MCP server.
  • Any MCP-capable AI client (Claude Code, Cursor, Codex, and others).
New to the engine? Read the Quickstart to understand submissions and the design system first, then come back to wire it into your agent.