npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gerardlopezdev/holyguide-mcp

v1.0.1

Published

MCP Server for Massimo Dutti HolyGuide Design System - Access design tokens, components, and documentation

Readme

HolyGuide MCP Server

npm version

MCP Server para el Design System HolyGuide de Massimo Dutti.

Este servidor permite a los asistentes de IA (como GitHub Copilot en VS Code) consultar el Design System en tiempo real para generar código que siga las guías de estilo oficiales.

🚀 Instalación

No necesitas instalar nada manualmente. Solo configura VS Code y usará npx automáticamente.

🔧 Configuración en VS Code

Añade esto a tu archivo .vscode/mcp.json en tu proyecto (o en settings.json global):

{
  "servers": {
    "holyguide": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@gerardlopezdev/holyguide-mcp"]
    }
  }
}

Reinicia VS Code y el MCP estará disponible.

🛠️ Herramientas disponibles

| Herramienta | Descripción | |-------------|-------------| | get_typography | Documentación de tipografías | | get_spacing | Documentación de espaciado (paddings, margins) | | get_colors | Documentación de colores | | get_flexbox | Helpers de flexbox | | get_buttons | Documentación de botones | | get_components | Lista de componentes disponibles | | get_templates | Lista de templates/plantillas | | get_page | Cualquier página específica de HolyGuide | | search_holyguide | Búsqueda en toda la documentación | | get_all_foundations | Toda la documentación de foundations |

💬 Ejemplos de uso

Una vez configurado, puedes pedirle al asistente:

  • "¿Cómo hago un botón que ocupe todo el ancho?"
  • "Dame las clases de padding responsive de HolyGuide"
  • "¿Qué tipografías debo usar según HolyGuide?"
  • "Genera un card siguiendo el Design System de Massimo Dutti"

🔄 Caché

El servidor cachea las respuestas durante 5 minutos para mejorar el rendimiento. Los datos se obtienen en tiempo real desde https://holyguide.es/

📝 Desarrollo local

# Clonar el repositorio
git clone https://github.com/glopezi1997/holyguide-mcp.git
cd holyguide-mcp

# Instalar dependencias
npm install

# Build
npm run build

# Ejecutar
npm start

📦 Publicar nueva versión

# Incrementar versión
npm version patch  # o minor / major

# Publicar
npm publish --access public

🤝 Contribuir

  1. Fork del repositorio
  2. Crear rama feature (git checkout -b feature/nueva-funcionalidad)
  3. Commit cambios (git commit -am 'Añade nueva funcionalidad')
  4. Push a la rama (git push origin feature/nueva-funcionalidad)
  5. Crear Pull Request

📄 Licencia

MIT