Taste Bank
Shared front-end style packs that coding agents can browse, fetch and apply to projects
- Pricing
- Open source
- Platforms
- CLI, API, self-hosted
- Version
- 0.2.0
- Listing updated
- today
Similar MCP servers
About Taste Bank
Taste Bank is an open-source MCP server for finance and payments. It is available on CLI, API, self-hosted and Web.
The README says Taste Bank is a library of visual design systems for coding agents, where each style is stored as a structured pack containing a SKILL.md usage guide, design tokens and HTML template snapshots. Instead of re-explaining a look in every new project, an agent can list styles, pull the full pack and build within its tokens.
Access runs through a CLI installed with npx taste-bank setup, which injects two skills into supported agents: one for browsing and applying styles, and one for packing and submitting a new style from an existing project. An MCP endpoint at tastebank.cloud is also offered as a legacy option that needs an invite code. Packs are validated against a zod schema, cached locally for three days, and can be pointed at a self-hosted backend through an environment variable.
It suits developers and designers who want their coding agents to produce consistent front-ends and who want to keep and share styles they already use. Submissions require an invite code and an ed25519 key pair, and go live only after maintainer review.
What it does
- One-command agent setup
- A single npx command installs the CLI and teaches supported coding agents how to use it.
- Complete style packs
- One call returns metadata, design tokens, SKILL.md rules, scoped CSS and HTML templates.
- Local pack caching
- Packs are cached for three days so the CLI can fall back when the server is unreachable.
- Signed style submissions
- Submissions, updates and deletions are signed with an ed25519 key that acts as the owner identity.
- Pack validation
- Style packs are checked against a zod schema locally before submission.
- Manual review queue
- New submissions are held for maintainer approval before becoming public.
Good for
- Have a coding agent build a landing page in an established visual style
- Keep a personal design style and reuse it across projects
- Extract the tokens and rules from one project and publish them as a shareable style
- Browse available front-end styles before starting a new interface
Pricing
Open source
MIT-licensed; no paid plan mentioned in the README.
Taste Bank FAQ
How do I install Taste Bank for my coding agent?
The README says to run npx taste-bank setup, which installs the CLI globally and injects the taste-bank skills into supported agents.
Do I need an account to use it?
Browsing and applying styles needs no auth according to the README. Submitting requires an invite code and a locally generated ed25519 key, and there are no accounts.
Can I host the backend myself?
The README says the CLI can be pointed at a self-hosted backend by setting the TASTEBANK_API environment variable.
Are submitted styles published immediately?
No. The README says submissions enter a review queue and go live only after maintainer approval.
Is Taste Bank free?
Yes. Taste Bank is open source, so you can use and self-host it for free.
What are the best alternatives to Taste Bank?
The closest alternatives to Taste Bank are Raven, StyleKit, Curio — design style library, tesserai and Standby Design MCP.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
