Polyglot SSG MCP
Let your agent drive builds and config across many static site generators—Zola, Hakyll, and dozens more—when shipping docs sites and marketing pages.
Overview
Polyglot SSG MCP is an MCP server for the Build phase that exposes twenty-eight static site generators in nineteen languages to coding agents through one server.
What is this MCP server?
- Unified MCP for 28 static site generators spanning 19 programming languages
- Includes Zola, Hakyll, and other non-JavaScript SSGs often skipped by generic site skills
- OCI delivery ghcr.io/hyperpolymath/poly-ssg-mcp:main with stdio transport (v1.0.0)
- Source at github.com/hyperpolymath/poly-ssg-mcp under title Polyglot SSG MCP
- Supports solo builders who mix Rust, Haskell, and mainstream JS frameworks for content sites
- 19 programming languages covered per catalog description
- Named examples include Zola and Hakyll
What problem does it solve?
Shipping docs with Zola, Hakyll, or niche SSGs forces solo builders to context-switch CLIs and docs while the agent cannot reliably invoke the right generator.
Who is it for?
Content-heavy solo projects, open-source maintainers, and polyglot developers who want agent help across many SSG CLIs—not only Next or Astro.
Skip if: Teams committed to one hosted CMS or a single framework with no interest in multi-generator static pipelines.
What do I get? / Deliverables
After adding poly-ssg-mcp, your agent can help build and tune static sites across many generators from a single MCP registration during docs work.
- Agent-driven builds and config changes across up to 28 static site generators
- Documentation and marketing static sites without bespoke MCP per framework
- Repeatable stdio MCP workflow for polyglot content repos
Recommended MCP Servers
Journey fit
Build is where documentation and static marketing sites take shape; an SSG MCP keeps generator choice flexible without custom scripts per stack. Docs subphase is the canonical shelf for static-site tooling that publishes READMEs, changelogs, and landing content from the repo.
How it compares
Multi-generator static-site MCP toolkit, not a WYSIWYG page builder skill or a single-framework deploy plugin.
Common Questions / FAQ
Who is Polyglot SSG MCP for?
It is for developers who publish docs or marketing sites with varied static generators and want Claude Code or Cursor to invoke the right SSG through MCP.
When should I use Polyglot SSG MCP?
Use it while building documentation, changelog sites, or static landing pages—especially when comparing Zola, Hakyll, or other language-native SSGs.
How do I add Polyglot SSG MCP to my agent?
Register stdio MCP using ghcr.io/hyperpolymath/poly-ssg-mcp:main, ensure local toolchains for your chosen generator, and restart your agent after updating MCP settings.