Lead Green MCP server

leadgreen.ai, the Lead Green site

Static, generated, no forms, no tracking. The only script is a short inline light/dark switch in the page shell. Serve the folder as-is (folder-style URLs; see Deploy).

index.html                      home
why/ index/ api/ mcp/ blog/ newsletter/ contribute/ about/   one index.html each (generated)
blog/<slug>/index.html          one folder per post (generated)
api/v1/                         the read-only JSON API (generated)
feed.xml sitemap.xml robots.txt llms.txt llms-full.txt .nojekyll   (generated)
assets/cards/*.png                                   (generated social cards, one number per page; needs Pillow and build/fonts)
assets/site.css                 the one stylesheet (hand-written)
assets/logo/                    the mark and lockups (SVG masters, light and dark), the icon master and its 512 px PNG
assets/social-card.svg .png     the 1200 by 630 link preview image (og:image); the PNG is rendered from the SVG
favicon.svg favicon.ico apple-touch-icon.png   site icons, cut from assets/logo/leadgreen-icon.svg
build/build.py                  the generator: reads build/data, build/pages, build/posts; writes everything above
build/layout.html               page shell: head, nav, footer, {{PLACEHOLDERS}}
build/pages/*.html              page bodies, one per page, with a meta block at the top
build/posts/YYYY-MM-DD-slug.html  blog posts, same s

Where this lives

• The working repository sits in Katonic's GitHub Enterprise organisation, which cannot host public repositories; changes are merged there first.
• The public mirror is katonic-dev/leadgreen-ai: master is pushed there after every merge, GitHub Pages serves leadgreen.ai from it, and it is where issues and pull requests from outside are opened. A change accepted there is merged into the working repository and reaches the mirror on the next push.
• The project's other homes (the Hugging Face dataset, the Zenodo DOI, Wikidata) are set in build/projecttext.py; the build writes them into the pages' JSON-LD sameAs, CITATION.cff and .zenodo.json. build/hfdataset.py assembles and pushes the dataset.

Build

From this folder:

python build/build.py

It renders every page and API file in memory first and refuses to write anything if a single {{PLACEHOLDER}} is unfilled or an em or en dash appears. Numbers on pages come only from build/data through placeholders defined in build/build.py; never type a figure into a page.

After any change to leadgreen-mcp/ or to the data, rebuild the wheel:

python -m pip wheel ./leadgreen-mcp -w dist --no-deps

The MCP server works with the mcp Python SDK 1.x and 2.x (guarded import in server.py). To exercise it, run any MCP client against python -m leadgreenmcp.server with PYTHONPATH=leadgreen-mcp and LEADGREENAPI_BASE set to the api/v1 folder; an example client script that checks the worked example (50 million tokens of Qwen 3 32B on H100 in Serbia = about 3,173 Wh and 2.12 kg CO2e) is described in the handover.

Preview: serve the folder locally, for example python -m http.server 8171 from the site root, so folder-style links resolve; opening the files directly also works for single pages.

Edit

Shortened. The full README is on GitHub.