Chrome Profile Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| profile_helper_prepareB | Prepare a profile-owned directory from an immutable stage; does not install it |
| profile_helper_updateC | Update an extension installed from its profile-owned directory, backing up and verifying loaded version |
| profile_helper_reconcileC | Reconcile a pending helper operation without repeating reload |
| profile_helper_rollbackB | Restore an artifact backup of a profile-owned extension and verify the loaded version |
| profile_helper_backupB | Back up a verified unpacked extension artifact from a paired profile, excluding profile and extension storage |
| profile_helper_stageC | Validate and stage an immutable artifact for a verified paired existing profile |
| profile_helper_reloadB | Reload in a paired existing profile using its explicitly authorized Chrome debugging channel; verify loaded version |
| profile_extensions_listC | List extensions in a paired existing profile |
| profile_extension_getC | Read an extension in a paired existing profile |
| profile_extension_set_enabledC | Enable or disable an extension in a paired existing profile and return Chrome readback |
| profile_listA | List profile names and report controlled, helper, policy and unmanaged availability; backend configuration is not runtime proof |
| profile_stageC | Stage content from a relative path under the manager artifacts directory; verify hash, key-derived identity and version |
| profile_installC | Install a staged controlled profile with CAS |
| profile_updateC | Update a controlled profile with CAS |
| profile_reloadC | Reload through a controlled pipe backend and verify loaded version |
| profile_backupC | Back up verified extension artifact with CAS; excludes profile and extension storage |
| profile_rollbackC | Restore backed-up extension artifact with CAS and Chrome readback |
| profile_reconcileC | Read back a pending operation without repeating it |
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 18 tools
The tool set has many parallel helper-vs-controlled operations such as profile_stage/profile_helper_stage, profile_reload/profile_helper_reload, and profile_backup/profile_helper_backup. Descriptions distinguish paired existing profiles from controlled profiles, but the overlapping action names create real misselection risk.
Almost all tools use lowercase snake_case with a consistent profile_ or profile_helper_ prefix. Minor deviations appear in resource/action ordering and pluralization, e.g. profile_extensions_list, profile_extension_get, and profile_extension_set_enabled.
The server exposes 18 tools, which is borderline heavy for the stated purpose. The duplication between controlled-profile and helper-profile workflows makes the surface feel larger than necessary.
The surface covers staging, install/update, reload, backup, rollback, reconcile, and basic extension read/list/enable operations. However, obvious lifecycle gaps remain, such as profile create/delete and extension uninstall/remove.