Skip to main content
Glama
Sign In
yundoun

hwms-mcp-server

by yundoun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hwms-mcp-server

No user-submitted related servers found.

    Related Servers

    • Arch-Master MCP

      NicolasAEV
      F
      license
      Not graded
      quality
      D
      maintenance
      Multi-stack scaffolding engine for generating production-ready module structures (NestJS, Java Spring, Python FastAPI) directly from an MCP-compatible AI client, reducing token usage for boilerplate code.
      -

    • mcp-garendesign

      lyw405
      A
      license
      B
      quality
      D
      maintenance
      Enables AI-driven frontend component design and code generation from natural language requirements. Supports Vue, React, and Angular with intelligent component decomposition, API design, and complete project generation.
      4
      3
      MIT

    • Next.js MCP Server

      samihalawa
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automate Next.js development including project scaffolding, React component generation, API route creation, and full-stack application workflows with TypeScript and Tailwind CSS support.
      MIT

    • Vibe Coder MCP Server

      ManonHussein848
      A
      license
      Not graded
      quality
      A
      maintenance
      Equips MCP-compatible AI assistants with tools for deep research, requirements and PRD generation, codebase mapping, context curation, task management, and fullstack starter-project scaffolding. It supports CLI, REPL, and server modes so developers can drive software development workflows through natural-language commands.
      22 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing available modules, resolving dependencies, generating a new scaffold, and adding a module to an existing project. There is no overlap in their primary functions, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_modules, resolve_dependencies, generate_scaffold, add_module. This predictable structure aids agent selection and comprehension.

    Tool Count5/5

    With 4 tools, the server is tightly scoped to the core workflow of module management: listing, dependency resolution, scaffolding, and adding. Each tool is essential and there is no bloat, making the count ideal.

    Completeness4/5

    The tool surface covers the main lifecycle of module management in a hybrid web app project. Minor gaps might include module update or removal operations, but the current set covers starting a project and extending it sufficiently.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources