Connect via MCP

Give your AI tools live access to your taste profile. Instead of copy-pasting a file, your tools pull your profile automatically whenever they need it.

Requires a published profile

MCP serves your published profile — the one you explicitly choose to share. Complete comparisons, then publish from your reveal page. Your private scores stay on your device.

Claude Code

claude mcp add tasteid https://tasteid.xyz/sse

Run in terminal

1.Run the command above in your terminal
2.Claude Code will now have access to your published tasteID profile
3.Ask Claude to "use my tasteID profile" when building UI

Claude Desktop

{
  "mcpServers": {
    "tasteid": {
      "url": "https://tasteid.xyz/sse"
    }
  }
}

~/Library/Application Support/Claude/claude_desktop_config.json

1.Add the config above to your Claude Desktop settings file
2.Restart Claude Desktop
3.Your taste profile will be available as a tool

Cursor

Name: tasteid
URL: https://tasteid.xyz/sse

Settings > MCP

1.Open Cursor Settings > MCP
2.Add a new MCP server with the config above
3.Your taste profile will be available in Composer

Available tools

get_taste_profile

Full design sensibility — principles, aesthetics, and overrides. Returns a creative brief formatted for the requesting tool.

Input: username, format (nl/json), target

get_design_principles

Just the constants — how you approach building, regardless of project. Complexity, hierarchy, errors, density, trust.

Input: username

MCP vs file export

File export (CLAUDE.md)

Static snapshot. Lives in your project. Private, works offline, versioned in git. Best for personal use.

MCP (live connection)

Live profile access. Updates propagate instantly. Requires a published profile. Best for sharing your taste with others or across all projects.

prefer a file? go to export →