
Finhay Plugins
Add finhay-plugins when you ship Finhay-branded product surfaces and need brand rules, Metabase querying via MCP, and legacy-service documentation in one Claude marketplace.
Overview
finhay-plugins is a plugin marketplace for the build phase that bundles Finhay brand guidelines, a Metabase MCP server, and a legacy service documentation plugin for Claude agents.
What is this marketplace?
- 3 plugins: finhay-brand-guidelines, finhay-metabase-mcp, document-legacy-service
- Brand plugin applies official Finhay Vietnam identity, typography, logo, and voice
- Metabase MCP ships with Finhay defaults for mb.vnsc.vn querying and SQL reporting
- document-legacy-service (v1.1.0) targets legacy reverse-engineering and Confluence-style product cards
- Finhay Team–authored marketplace with design, data, and documentation categories
- Marketplace ships 3 plugins with explicit version tags on each listing
- Plugins span design, data/analytics MCP, and documentation categories per marketplace metadata
What problem does it solve?
Teams rebuilding Finhay-facing features juggle brand consistency, analytics queries, and legacy service docs across disconnected prompts and manual Metabase clicks.
Who is it for?
Finhay engineers and contractors—or builders modeling a similar trio of brand, data MCP, and legacy doc skills in one marketplace.
Skip if: Generic indie projects with no Finhay brand or mb.vnsc.vn Metabase estate who only need unrelated MCP servers.
What do I get? / Deliverables
After registration, you can enable brand-aligned artifacts, default-config Metabase MCP queries, and structured legacy documentation from one marketplace.
- Brand-consistent UI and marketing drafts via finhay-brand-guidelines v1.0.0
- SQL and reporting oriented Metabase sessions via finhay-metabase-mcp v1.0.0
- Legacy service documentation outputs from document-legacy-service v1.1.0
Plugins in this marketplace
3 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
The bundle mixes MCP data access, brand-compliant UI work, and legacy reverse-engineering—capabilities you wire while building the product and its agent tooling. Two of three plugins are integrations (Metabase MCP, legacy doc pipeline); integrations is the common shelf for MCP plus doc automation alongside build-time brand enforcement.
How it compares
Org-specific three-plugin pack (brand + Metabase MCP + legacy docs), not a single open-source skill or FDIC data server.
Common Questions / FAQ
Who is Finhay Plugins for?
It is for Finhay Team workflows and agents that must honor Finhay Vietnam brand rules, query Metabase with Finhay defaults, and document legacy services.
When should I use Finhay Plugins?
Use it during builds and doc passes where UI must match Finhay identity, analytics need mb.vnsc.vn Metabase access, or legacy services need product-card style documentation.
How do I add Finhay Plugins to my agent?
Register Finhay Plugins in your Claude marketplace, then enable finhay-brand-guidelines, finhay-metabase-mcp, and/or document-legacy-service from their ./plugins paths.