works.jinn/gateway — MCP Server
The Jinn gateway MCP consolidates brand DNA, brand kits, design systems, and agency tools behind a single bearer token. It provides a centralized Model Context Protocol server to manage and access branding assets and design-system tooling through authenticated requests.
🛠️ Key Features
- Brand DNA and brand kits as accessible resources
- Design systems and agency tools centralized under one bearer token
- MCP server providing structured context for downstream apps
- Token-based authentication for secure access
🚀 Use Cases
- Deliver consistent brand assets across projects
- Centralize design-system components for rapid integration
- Authenticate and serve branding contexts to design tooling
⚡ Developer Benefits
- Simplified authentication with a single bearer token
- Clear, centralized source of brand and design-system context
- Improve consistency and reusability across frontend and design tooling
⚠️ Limitations
- Description limited to provided metadata; may require additional endpoints for full asset management