Run a Jekyll build to verify your site compiles after component changes. Captures exit code, output, and _site path without arbitrary shell commands.
MIT
650,536 tools. Updated 2026-10-14 07:08
"Jekyll" matching MCP tools:
- Return a high-level summary of a Jekyll project—site detection, layout, include and component counts, SCSS/JS/docs presence, and write mode—to orient agents before they inspect or edit files.MIT
- Read Jekyll _config.yml settings with sensitive keys redacted so agents can inspect site configuration without exposing API keys, tokens, or credentials. Read-only.MIT
- Create reusable Jekyll Liquid components with SCSS, docs, and example files. Use for new UI components, not one-off page markup.MIT
- Diagnose common configuration and environment problems in Jekyll projects without altering source files.MIT
- Validates Jekyll project components, Liquid patterns, and front matter, optionally running a build to return structured errors and warnings without executing arbitrary shell commands.MIT
Matching MCP Servers
- AlicenseAqualityAmaintenanceEnables AI agents to understand, inspect, create, validate, build, and document Jekyll component frameworks through Jekyll-aware tools, resources, prompts, sandboxed filesystem access, and configurable write modes.231,072 npmMIT
- AlicenseNot gradedqualityDmaintenanceIndexes and searches Jekyll blog content, enabling AI assistants to search posts by keyword/category/tags, retrieve full post content, compare drafts against published posts, and analyze blog categories and tags.1MIT
- Generate Markdown files for technical documentation in code repositories. Supports auto table of contents, YAML frontmatter, and full markdown syntax for GitHub-ready content.MIT
- Read an SCSS file in a Jekyll project to get its source and analysis of imports, variables, mixins, and selectors. Provide a relative path from the project root for read-only inspection.MIT
- Lists Liquid include files under _includes, excluding components/ and sections/ subtrees. Read-only; does not execute Liquid.MIT
- Generate correctly-formatted frontmatter for Hugo, Jekyll, Astro, Next.js, Dev.to, Hashnode, and Ghost. Auto-extracts description, reading time, slug, and suggests tags from article content. No external API calls required.MIT
- List SCSS/CSS files under the SCSS root and detect architecture layers (tokens, mixins, base, utilities, components, sections) to understand stylesheet structure before editing. Read-only.MIT
- List all detected reusable Jekyll components with paths to Liquid, SCSS, JavaScript, docs, and examples to discover existing components before creating new ones.MIT
- Deletes a Jekyll component and its associated Liquid, SCSS, JS, docs, and example files. Requires confirm: true and full-write mode to proceed.MIT
- Scan a Jekyll project to map its architecture—configs, directories, layouts, includes, components, sections, SCSS, and JS—before creating or modifying components.MIT
- Retrieve full details for a Jekyll component by name, including Liquid/SCSS/JS/docs source, parameters, variants, accessibility notes, and classes before editing or reviewing. Read-only.MIT
- Lists design tokens found in SCSS files, categorized by color, spacing, typography, and more. Read-only, it helps inspect design systems in Jekyll components.MIT
- Read a Liquid include by name or path to inspect its source, front matter, parameters, and syntax. Read-only, never executes Liquid.MIT
- Retrieve the source, front matter, and analysis of a Jekyll Liquid layout by name or relative path without executing it.MIT
- Lists all Liquid layout files in the _layouts directory without executing them, helping AI agents inspect Jekyll project structures.MIT
- Retrieve design tokens by name fragment or category, such as color, spacing, or CSS variable, from a Jekyll component framework. Read-only lookup.MIT
- Validate Jekyll component files, Liquid syntax, SCSS, docs, accessibility hints, and parameter consistency; returns structured errors and warnings for fixing issues.MIT