Chrome Profile Manager
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Chrome Profile Manager list the unpacked extensions in my paired Chrome profile"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Chrome Profile Manager
An experimental MCP server and native messaging bridge for inspecting and managing unpacked Chrome extensions in an explicitly paired profile. It is a standalone candidate component for MCP hosts; it is not part of GPTAdmin core.
The project currently supports profile discovery and a profile-scoped extension bridge on Linux and macOS test setups. Ordinary user profiles, Windows lifecycle operations, permanent chooser installation, and modern MCP Tasks/subscriptions remain limited or unverified. Read the capability and limitation notes in docs/CHROME_PROFILE_MANAGER_MCP.md before use.
Install
From a checkout with Python 3 and network access for the pinned wheel:
python3 install_chrome_profile_manager.py \
--prefix "$HOME/.local/lib/chrome-profile-manager-1" \
--state-dir "$HOME/.local/state/chrome-profile-manager"The command creates a private installation and prints an MCP registration object. Add that object to the MCP host you operate, then configure a disposable Chrome profile with the bridge provisioner. Installation does not open, copy, or modify an existing browser profile.
Related MCP server: chrome-in-harness
Check the source
python3 -m pip install -r chrome_profile_manager_requirements.txt pytest
python3 -m pytestThe normal test suite uses temporary state and does not require a real Chrome profile. Real browser checks are opt-in and documented separately. The qa/gptadmin directory preserves historical checks that require a private GPTAdmin or ShellMCP installation.
Documentation
MCP capabilities, setup, and limitations: docs/CHROME_PROFILE_MANAGER_MCP.md
Bridge protocol and profile binding: chrome_profile_manager_bridge/README.md
Current experimental status: docs/STATUS.md
Archived QA evidence: chrome_profile_manager_bridge/QA_EVIDENCE.md
License
AGPL-3.0-or-later; see LICENSE.
Available Tools
18 toolsprofile_backupC
Back up verified extension artifact with CAS; excludes profile and extension storage
Inputs: profile_id (required), expected_version (required), extension_id.
profile_extension_getC
Read an extension in a paired existing profile
Inputs: profile_id (required), extension_id (required).
profile_extension_set_enabledC
Enable or disable an extension in a paired existing profile and return Chrome readback
Inputs: enabled (required), profile_id (required), extension_id (required).
profile_extensions_listC
List extensions in a paired existing profile
Inputs: profile_id (required).
profile_helper_backupB
Back up a verified unpacked extension artifact from a paired profile, excluding profile and extension storage
Inputs: profile_id (required), extension_id (required), expected_version (required).
profile_helper_prepareB
Prepare a profile-owned directory from an immutable stage; does not install it
Inputs: stage_id (required), profile_id (required).
profile_helper_reconcileC
Reconcile a pending helper operation without repeating reload
Inputs: profile_id (required), extension_id (required).
profile_helper_reloadB
Reload in a paired existing profile using its explicitly authorized Chrome debugging channel; verify loaded version
Inputs: profile_id (required), extension_id (required), expected_version (required), expected_current_version (required).
profile_helper_rollbackB
Restore an artifact backup of a profile-owned extension and verify the loaded version
Inputs: backup_id (required), profile_id (required), extension_id (required), expected_version (required).
profile_helper_stageC
Validate and stage an immutable artifact for a verified paired existing profile
Inputs: digest (required), version (required), profile_id (required), source_path (required), +1 more.
profile_helper_updateC
Update an extension installed from its profile-owned directory, backing up and verifying loaded version
Inputs: stage_id (required), profile_id (required), expected_version (required).
profile_installC
Install a staged controlled profile with CAS
Inputs: stage_id (required), profile_id (required), expected_version.
profile_listA
List profile names and report controlled, helper, policy and unmanaged availability; backend configuration is not runtime proof
profile_reconcileC
Read back a pending operation without repeating it
Inputs: profile_id (required), extension_id.
profile_reloadC
Reload through a controlled pipe backend and verify loaded version
Inputs: profile_id (required), expected_version (required), extension_id.
profile_rollbackC
Restore backed-up extension artifact with CAS and Chrome readback
Inputs: backup_id (required), profile_id (required), expected_version (required), extension_id.
profile_stageC
Stage content from a relative path under the manager artifacts directory; verify hash, key-derived identity and version
Inputs: digest (required), version (required), profile_id (required), source_path (required), +1 more.
profile_updateC
Update a controlled profile with CAS
Inputs: stage_id (required), profile_id (required), expected_version (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Build, run, inspect, and continue AgentScript workflows on connected Super Chrome and Mac clients.
Launch, inspect, control, and share isolated cloud browsers for your agents.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to drive individually named Chrome profiles, providing tools for tabs, navigation, page interaction, screenshots, JavaScript evaluation, console logs, and network inspection over stdio without a TCP port.MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to drive the user's real Chrome profile through a Chrome extension bridge, with tools for navigation, accessibility snapshots, ref-based interactions, console/network reading, screenshots, tab management, and restricted script evaluation.1MIT
- AlicenseBqualityBmaintenanceEnables agents to inspect localhost web applications through Chrome DevTools Protocol by listing Chrome targets, attaching to a page, capturing and querying network, console, navigation, and WebSocket events, and managing ephemeral sessions.81MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and CLI users to drive their locally installed Google Chrome through a dedicated persistent profile over the DevTools Protocol, so they can navigate open HTTP/HTTPS sites, manage tabs, and inspect pages while keeping existing sign-ins and cookies.MIT