Skip to main content
Glama

Related Servers

Alternatives to jekyll-component-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to index and search local skill libraries, persist and resume task checkpoints, and run validated workflow plans with controlled approval and write permissions.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Acts as the 'Hands and Eyes' for an Autonomous AI Agent, bridging Large Language Models and your local development environment to enable safe file manipulation, context reading, command execution, and documentation verification.
      9
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to safely explore directories, read files, search content by pattern or filename, and edit files with checksum verification and dry-run preview within sandboxed filesystem access.
      9 npm
      75
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to detect development environments, install missing tools, scan local code projects, and generate visual reports.
      10 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with production-ready integrations for GitHub repository management, sandboxed code execution, SFTP file operations, web search and scraping, YouTube, Google Workspace, Notion, and more.
      -

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are cleanly partitioned by resource (project, layout, include, component, scss, token, docs) with distinct actions. A few pairs invite mild confusion—jekyll_project_info vs jekyll_project_scan, jekyll_validate vs jekyll_component_validate, and jekyll_validate vs jekyll_build vs jekyll_doctor—but their descriptions clearly delineate scope.

    Naming Consistency5/5

    Every tool follows the exact jekyll_{resource}_{action} snake_case convention (e.g. jekyll_component_create, jekyll_scss_list, jekyll_token_update). The pattern is uniform across all 23 tools with no camelCase or verb-style deviations.

    Tool Count4/5

    23 tools is on the higher side but the domain (components, layouts, includes, SCSS, tokens, docs, validation, build) is genuinely broad and the tools are cleanly grouped. Each entry has a distinct function, so the count is defensible rather than bloated.

    Completeness4/5

    Strong coverage of a read-and-manage workflow: full list/get/create/delete/validate for components plus project info, tokens, docs, build, and doctor. Notable gap: no jekyll_component_update (and no SCSS update/delete), so editing an existing component's files has no dedicated tool despite guidance to 'use before editing.'

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues