Part II: Install and deploy

memo-mcp has no installer and no service to register. Installing it means putting one binary on disk and telling an MCP client how to start it.

• Release archives: download, verify and place the binary.
• Build from source: reproducible pure-Go builds.
• Connecting MCP clients: Claude Code, Claude Desktop and any stdio client.
• Knowledge bases and MEMO_HOME: one file per KB, per-project setups.
• Upgrading and migrations: schema versions and what to run after an upgrade.
• Air-gapped installs: no network at runtime, not even the model download.