Your Jekyll workflow, in context

Better building blocks for Jekyll.

Give your AI assistant the context and tools to explore, create, and validate reusable Liquid components—right inside your project.

Open source Node.js 20+ Works with MCP clients

A useful assistant starts with context

From project insight
to polished components.

Keep discovery, implementation, and validation together in one Jekyll-aware toolset.

01

Understand

Know your Jekyll project

Scan layouts, includes, components, styles, and configuration before making a change. Sensitive configuration values are redacted.

02

Create

Build reusable components

Scaffold a Liquid component with matching SCSS, documentation, and an example—then preview it before you use it.

03

Validate

Keep quality in the loop

Check Liquid patterns, styles, docs, accessibility hints, and parameter consistency. Build and doctor tools stay Jekyll-focused.

A simple, safe rhythm

Keep your project
in the driver's seat.

Use your existing MCP-compatible editor. The server works within the Jekyll root you choose and keeps destructive actions gated.

Read the setup guide
  1. 01

    Connect

    Point your MCP client at the server and your Jekyll project root.

  2. 02

    Explore

    Start with project info, then inspect components and conventions before editing.

  3. 03

    Create with confidence

    Preview generated files, apply the change, and validate the component or site.

Designed for safer changes

Useful tools.
Clear boundaries.

  • Paths stay inside your configured project root.
  • Read-only by default for destructive operations.
  • Build commands are limited to Jekyll tasks.
  • Sensitive config values are redacted.

Ready when you are

Bring your Jekyll
project into focus.

Run it with npx—no global install required. Node.js 20 or newer is required.

View package on npm
Terminal
# Start the server for your Jekyll project
npx -y jekyll-component-mcp --root /path/to/site
MCP client configuration
{
  "command": "npx",
  "args": ["-y", "jekyll-component-mcp",
           "--root", "/path/to/site"]
}