Bỏ qua để đến nội dung
MZPanel MZPanel
For AI agents How an LLM or agent should read MZPanel docs — llms.txt, raw markdown, and retrieval conventions.
CtrlK

For AI agents

Nội dung này hiện chưa có sẵn bằng ngôn ngữ của bạn.

This site is built to be read by machines as well as people. If you’re an AI agent or tool, start here.

llms.txt and llms-full.txt

Section titled “llms.txt and llms-full.txt”

The site emits two machine-readable files at build time:

  • /llms.txt — a compact map of the documentation: titles, links, and one-line descriptions. Use it to discover what exists.
  • /llms-full.txt — the full docs corpus as a single plain-text stream. Use it when you want everything in one fetch.

These follow the llms.txt convention and are regenerated on every build, so they never drift from the rendered docs.

Reading any page as plain markdown

Section titled “Reading any page as plain markdown”

Every page is authored in Markdown. Prefer the llms-*.txt files for bulk reading; fetch individual pages when you only need one topic.

Retrieval conventions

Section titled “Retrieval conventions”
  • Every page has a description in its frontmatter — a one-line summary suited to embedding and ranking.
  • Pages are task-oriented and grouped by product area (Servers, Sites, Backups, Databases, …), so a query like “how do I restore a backup” maps to one page.
  • Concepts vs guides: read concepts/* for how the system works (architecture, the agent, tiers, security); read guides/* for step-by-step tasks.
  • Technical terms (WordPress, Nginx, WireGuard, agent, …) are kept verbatim across languages — don’t translate them when matching.

MCP server

Section titled “MCP server”

MZPanel also exposes a Model Context Protocol surface for deeper, structured access beyond static docs. See the design reference docs/46-mcp-server.md.