TasteMaker
Wire a read-only TasteMaker brand kit and generated agent skill into Claude Code or Cursor so UI and copy stay on-brand while you ship.
Overview
TasteMaker MCP is a MCP server for the Build phase that read-only pulls your TasteMaker brand kit and generated Agent Skill into your coding tool.
What is this MCP server?
- Streamable HTTP remote at tastemakerdev.com/mcp (MCP schema 2025-12-11)
- Read-only pull of TasteMaker brand kit plus a generated Agent Skill into your coding tool
- Open-source server repo on GitHub (ryan-the-brodsky/tastemaker)
- No write path—safe for agents that should not mutate brand source of truth
- Pairs design tokens and narrative tone with agent workflows in one MCP connection
What problem does it solve?
Builders waste hours re-pasting brand PDFs and tone notes into every agent session while drift creeps into UI and copy.
Who is it for?
Indie SaaS or content founders who already maintain a TasteMaker brand kit and want Claude Code or Cursor to honor it during implementation.
Skip if: Teams that need agents to edit or publish brand assets back to TasteMaker, or builders with no TasteMaker account or kit.
What do I get? / Deliverables
Your agent loads consistent brand kit and skill context from MCP so new screens and prompts align with TasteMaker without manual exports each sprint.
- In-session access to TasteMaker brand kit fields via MCP tools
- Generated Agent Skill content available to the coding agent read-only
- Consistent brand-aware suggestions during frontend and copy edits
Recommended MCP Servers
Journey fit
Brand kits land on the Build shelf because they are consumed while implementing surfaces, marketing pages, and agent prompts—not during raw idea research. Frontend is the canonical subphase: colors, typography, voice, and skill exports directly affect landing pages, apps, and in-editor agent behavior.
How it compares
MCP integration to a hosted brand kit, not a local Figma or design-token CLI skill.
Common Questions / FAQ
Who is TasteMaker MCP for?
Solo builders and small teams using TasteMaker who want read-only brand and agent-skill context inside MCP-enabled coding tools.
When should I use TasteMaker MCP?
Use it during Build (and Validate landing polish) whenever you implement UI, marketing pages, or agent prompts that must match an existing TasteMaker brand kit.
How do I add TasteMaker MCP to my agent?
Register the streamable-http remote https://tastemakerdev.com/mcp/ in your MCP client per Skillselion’s server entry, then connect from Claude Code, Cursor, or another compatible agent.