seite
About
AI-native static site generator with built-in MCP server. Build sites, create content, apply themes, search docs, and deploy via Claude Code or any MCP client.
Details
- Author
- seite-sh
- Categories
- Developer Tools, Other, AI, Knowledge Base
Jump to
Setup
Install seite in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/seite-sh/seite
Follow the installation instructions in the repository README, then restart your MCP client.
A static site generator where Claude Code is the interface.
You already have Claude Code. seite gives it something to work on.
seite agent "write a post about our v1 launch — here are the notes: ..." seite agent "redesign the homepage hero, we just pivoted to B2B" seite agent "create changelog entries for these release notes: ..." seite agent # interactive session
The agent reads your config, your templates, and your existing content before writing anything. Output lands in the right directory with the right frontmatter. You review a diff and ship it.
No new subscription. No new UI to learn. No new commands. Just the Claude Code subscription you already have — now it can manage your whole website.
curl -fsSL https://seite.sh/install.sh | sh seite init mysite --title "My Site" --collections posts,docs,pages cd mysite && seite serve
Most static site generators produce HTML and stop there. seite builds forthree audiences at once:
- Browsersget pages with full SEO metadata, Open Graph, Twitter Cards, and JSON-LD structured data
- LLMsgetllms.txt,llms-full.txt, and a.mdcopy of every page for direct consumption
- AI toolsget a built-in MCP server that exposes your entire site as structured resources
All from Markdown + YAML frontmatter. No JavaScript runtime. No build dependencies. One binary does everything. 331 tests, 139 unit and 192 integration.
seite agentspawns Claude Code with full site context — config, content inventory, templates, and available commands. No API keys, no setup. Uses your existing Claude Code subscription.
seite initgenerates.claude/CLAUDE.mdwith your site's full schema so the agent is oriented before it writes a single character. Output lands in the right directory, with the right frontmatter, following your conventions. You review a diff and ship it.
seite agent "write a post about our v1.2 release — here are the notes: ..." seite agent "rewrite the homepage hero, our positioning shifted to B2B" seite agent "generate docs stubs for each CLI command" seite agent # interactive session
seite mcpruns a Model Context Protocol server over stdio. Claude Code auto-starts it via.claude/settings.json, generated byseite init. Any MCP-compatible AI tool can use it.
Resources—seite://docs,seite://config,seite://content,seite://themes,seite://trust
Tools—seite_build,seite_create_content,seite_search,seite_apply_theme,seite_lookup_docs
This means your AI tool doesn't just have read access to your site — it has a structured interface to build, search, and modify it.
Every build generatesllms.txt(summary) andllms-full.txt(complete markdown) for LLM indexing, plus a.mdcopy of every page. Multilingual sites get per-language versions. Traditional SEO and GEO handled in one pipeline, automatically.
curl -fsSL https://seite.sh/install.sh | sh
VERSION=v0.1.0 curl -fsSL https://seite.sh/install.sh | sh
seite init mysite --title "My Site" --collections posts,docs,pages cd mysite seite serve
Openhttp://localhost:3000. Edit content incontent/, templates intemplates/. Live reload on every change.
# Create content seite new post "Hello World" --tags intro,rust seite new doc "Getting Started" seite new changelog "v1.0.0" --tags new,improvement # Deploy seite deploy # commit, push, build, deploy seite deploy --dry-run # preview what would happen seite deploy --setup # guided first-time setup
seite buildruns a 13-step pipeline and produces:
dist/ ├── index.html ├── posts/ │ ├── hello-world.html # HTML for browsers │ └── hello-world.md # Markdown for LLMs ├── docs/ │ └── getting-started.html ├── feed.xml ├── sitemap.xml ├── search-index.json ├── robots.txt ├── llms.txt ├── llms-full.txt ├── 404.html └── static/
Every HTML page includes canonical URLs, Open Graph tags, Twitter Cards, JSON-LD structured data, and a link to its markdown alternate.
seite collection add changelog seite new changelog "v2.0" --tags new,breaking
Six themes ship with the binary — no downloads, no CDNs:
seite theme list seite theme apply dark seite theme create "neon cyberpunk on black" seite theme install https://example.com/t.tera seite theme export my-theme
Filename-based translations. Single-language sites need no config.
content/posts/ ├── hello-world.md → /posts/hello-world ├── hello-world.es.md → /es/posts/hello-world └── hello-world.fr.md → /fr/posts/hello-world
[languages.es] title = "Mi Sitio" [languages.fr] title = "Mon Site"
# seite.toml — minimal [site] title = "My Site" base_url = "https://example.com" [[collections]] name = "posts"
Drop YAML, JSON, or TOML indata/and access in any template:
# data/nav.yaml - title: Blog url: /posts - title: Docs url: /docs
Available as{{ data.nav }}in all templates.
seite workspace init my-workspace seite workspace add blog --collections posts,pages seite workspace add docs --collections docs seite build --site blog seite serve seite deploy
seite deploy seite deploy --dry-run seite deploy --setup seite deploy --domain example.com
[deploy] target = "cloudflare" # or "github-pages" or "netlify"
seite initauto-generates the CI workflow for your chosen target.
seite collectsanonymous, opt-outusage telemetry to understand which commands are used and whether they succeed. No personal data, no file paths, no content.
What is never collected:file paths, site domains or URLs, page content, command arguments or flag values, environment variables, usernames, or any stable identifier.
Data is sent to thecli.seite.shpartition — a dedicated namespace that is completely separate from your site's own analytics. Full details:seite.sh/telemetry
seite telemetry off # persisted preference (survives shell restarts)
Or set an environment variable for one run or in your shell profile:
export SEITE_TELEMETRY=0 # disable via env var export DO_NOT_TRACK=1 # respects the universal DO_NOT_TRACK standard
Telemetry is also automatically disabled in CI (when theCIenvironment variable is set to any non-empty value). Check your current status:
seite telemetry status seite telemetry on # re-enable if you opted out
- Getting Started
- Configuration
- Collections
- Templates
- Shortcodes
- Multi-language
- Deployment
- CLI Reference
- Trust Center
seite is early and issues, PRs, and feedback are genuinely welcome. Especially useful:
- Bug reportswith a repro case (even a minimalseite.toml+ content file)
- New theme ideas— open an issue first to align on direction before building
- Docs improvements— if something confused you, it'll confuse others
- Real-world usage— if you build something with seite, share it
git clone https://github.com/seite-sh/seite cargo build cargo test # 331 tests (139 unit + 192 integration) cargo clippy # must be zero warnings cargo fmt --all
Open an issue before starting a large PR — saves everyone time.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Share your team's Coding Best Practices with Cursor, VS Code, Claude code, Windsurf, JetBrains IDEs and other coding tools supporting remote MCP connection.
Lance is an agent that runs on its own cloud Mac and handles everything on the App Store Connect side of shipping an iOS app. It connects to coding agents like Claude Code and Codex through MCP and takes over the parts they can't do: creating apps on App Store Connect, setting up notifications / widgets, filling out listing metadata, uploading builds to TestFlight, submitting for review, and responding to App Review feedback. Because it has its own Mac, it can also build, run, and test users' apps and capture screenshots.
AI-powered semantic search over React documentation for Claude, Cursor, and other MCP clients.
A universal MCP server that connects to any Storybook site and extracts documentation in real-time using Playwright. Use it with any AI or client that supports MCP (Model Context Protocol)—Cursor, Claude Desktop, Windsurf, or other MCP hosts.
Exposes WebPinch tasks, projects, site audits, and stats as MCP tools/resources/prompts for Claude Code, Cursor, and other MCP clients.
Access WordPress documentation and development tools.
The DataFast MCP server lets MCP-compatible clients such as Codex, Claude Code, and Cursor query your analytics and manage your account through natural language.
Inkrun's remote MCP server lets AI agents like Claude turn Markdown into themed, consistent and reproducible on-brand PDFs with a single tool call
Transform your scattered documentation into AI-ready knowledge that works seamlessly with Claude, Cursor, VS Code, and other AI tools.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





