
Polyglot SSG MCP
- hyperpolymath/poly-ssg-mcp
Polyglot SSG MCP is an MCP server that exposes twenty-eight static site generators in nineteen languages to coding agents through one server.
About
Polyglot SSG MCP unifies agent access to twenty-eight static site generators across nineteen languages, including Zola and Hakyll, so developers can scaffold, configure, and rebuild docs or marketing sites without memorizing every CLI flag. It belongs on the Build shelf under docs because most products need a fast, versioned site long before heavy app UI work finishes. Run the Hyperpolymath OCI image with stdio MCP, point your agent at the generator you are trying this week, and iterate on templates, content pipelines, and deploy artifacts from the IDE. Complexity is intermediate: you still need the language toolchains each SSG expects, but the MCP layer removes one-off automation scripts. Use it alongside your hosting choice in Ship/Launch later; here it accelerates getting readable documentation and landing pages out of the repository.
- 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
Polyglot SSG MCP by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add PolyglotSSGMCP -- npx -y hyperpolymath/poly-ssg-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Repository | hyperpolymath/poly-ssg-mcp ↗ |
|---|
What it does
Let your agent drive builds and config across many static site generators—Zola, Hakyll, and dozens more—when shipping docs sites and marketing pages.
Who is it for?
Content-heavy 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 you get
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
By the numbers
- 28 static site generators
- 19 programming languages covered per catalog description
- Named examples include Zola and Hakyll
Recommended MCP Servers
How it compares
Multi-generator static-site MCP toolkit, not a WYSIWYG page builder skill or a single-framework deploy plugin.
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.