agy-profiles
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_PROFILES_DIR | No | Overrides the profile storage root. By default, profiles are stored under /Volumes/Dev/.antigravity-profiles when writable on macOS, or ~/.antigravity-profiles. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| profile_listA | List all isolated Antigravity sandbox profiles, host binaries, and live status. |
| profile_inspectB | Inspect one sandbox profile, its permissions, symlinks, runtime PIDs, and Evidence record. |
| profile_createB | Create a hardened isolated profile directory with 0700/0600 permissions and optional sanitized config inheritance. |
| profile_updateC | Update profile metadata, auth mode, or symlink policy and reconcile sandbox directories. |
| profile_launchC | Launch Antigravity Hub or IDE strictly sandboxed inside the profile directory. |
| profile_stopB | Stop verified running processes owned by a sandbox profile using staged SIGTERM then SIGKILL. |
| profile_repairC | Clean stale Chromium locks when stopped and reconcile sandbox .zshenv and permissions. |
| profile_cloneB | Clone a stopped sandbox profile to a new profile slug with freshly locked .zshenv HOME. |
| profile_deleteC | Delete a sandbox profile and its macOS launchers after unlinking managed symlinks safely. |
| launcher_buildC | Compile a macOS Spotlight/Dock .app shim for launching a sandboxed profile. |
| launcher_removeC | Remove the macOS .app launcher shim associated with a sandbox profile. |
| system_doctorB | Inspect host Antigravity bundles, sandbox root permissions, stale locks, and isolation state. |
| obligations_verifyB | Run live security self-checks across isolation, MCP scrubbing, PID matching, and CSRF guards. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Profile lifecycle operations are clearly distinct: list, inspect, create, update, launch, stop, repair, clone, delete. Launcher build/remove are separate macOS app management tools. The only mild overlap is system_doctor versus obligations_verify, both diagnostic/security-oriented, but their descriptions distinguish host inspection from security control self-checks.
All tools use snake_case and a predictable resource_action pattern: profile_*, launcher_*, system_doctor, obligations_verify. The convention is consistent across the entire set and easy to parse.
13 tools is well within a reasonable range for a sandbox profile management server. Each tool covers a distinct lifecycle, launcher, or diagnostic responsibility, with no obviously redundant entries.
The surface covers full profile lifecycle: list, inspect, create, update, launch, stop, repair, clone, and delete. Launcher creation/removal and system/security verification are also included, leaving no obvious CRUD or operational gaps.