seite_buildLABSCO SUMMARY
The site is the tool surface, not just files on disk.
Most generators leave an agent to infer conventions from your directory tree. Here the config, content inventory, themes and the generator's docs come back as MCP resources, and building, searching and theming are calls rather than shell guesses. The telemetry default is the one thing to decide before you install: on unless you turn it off, and there is a documented switch for every way you might want to.
What it is
A static site generator that ships an MCP server as a first-class surface. seite mcp runs over stdio, and seite init writes the .claude/settings.json that starts it automatically, so an assistant does not just read your content/ folder — it can build the site, search it, apply a theme and look up the generator's own documentation through typed calls. Everything is Markdown plus YAML frontmatter; one binary, no JavaScript runtime.
What you get
- A build triggered and a page created from the conversation —
seite_build,seite_create_content - The site searched, and a theme applied, without leaving the client —
seite_search,seite_apply_theme - The generator's own documentation queried, so the agent stops guessing at frontmatter and config keys —
seite_lookup_docs - Five resources exposing the site as structured context:
seite://docs,seite://config,seite://content,seite://themes,seite://trust - Output built for machine readers as well as browsers: every build writes
llms.txt,llms-full.txtand a.mdtwin of each page, alongside Open Graph, Twitter Cards and JSON-LD
Requirements
No account and no key. Install the binary with curl -fsSL https://seite.sh/install.sh | sh on macOS or Linux, irm https://seite.sh/install.ps1 | iex on Windows, or cargo install seite from source. Six themes and six collection presets are compiled in — nothing is fetched from a CDN at build time. Usage telemetry is on by default and opt-out: seite telemetry off persists the choice, SEITE_TELEMETRY=0 or DO_NOT_TRACK=1 does it by environment, and it is disabled automatically when CI is set.
Setup effort
Follow the published steps — curl -fsSL https://seite.sh/install.sh | sh
USE CASES
01
Publishing a post from notes without opening the repo
Have the agent read your config and existing content, create the page in the right collection with the right frontmatter, and build — then review the diff yourself before shipping.
02
Finding every page that mentions something you are about to change
Search across the site through the server rather than grepping, and read the matching content back as structured context.
03
Trying a different look
Apply one of the six bundled themes — default, minimal, dark, docs, brutalist, bento — and rebuild to see it, with no download step.
04
Stopping the agent from inventing config keys
Point it at the docs lookup so frontmatter fields and seite.toml options come from the generator itself.
5 tools
Listed in project docs. Your client may show a different list.
seite_create_contentseite_searchseite_apply_themeseite_lookup_docsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
curl -fsSL https://seite.sh/install.sh | sh
seite init mysite --title "My Site" --collections posts,docs,pages
cd mysite
seite serveFor Claude Code there is nothing to add: seite init generated .claude/settings.json in the site folder, so Claude Code starts the MCP server (seite mcp, over stdio) itself when you open it there.
