The Inventory & Profile Model
v1.0
·
Updated 5 days ago
The Inventory & Profile Model
Each server has its own profile as a Markdown file at context/servers/<name>.md. The plugin directory itself is your workspace.
What a profile contains
| Section | Content |
|---|---|
| Connection | host, port, user, key_path, connect_timeout_seconds |
| Identity | description, os, arch, hostname, docker_available, docker_cmd, sudo_passwordless |
| Scoped Operations | the allowed operations (scopes) as checkboxes |
| Protected Resources | critical_compose_projects, protected_paths |
| Discovered State | latest disk, OS and uptime from /diag |
Your data stays local
Real profiles, the active server and the generated inventory are git-ignored:
context/servers/*.md— the real server profilescontext/active-server— the active servercontext/inventory.md— the generated overview
Only templates (e.g. EXAMPLE.md.template) live in the repository. So hosts, users, ports or keys never land in version control — and your inventory survives a claude plugin update unscathed.