cdp_navigateLABSCO SUMMARY
Authentication is where most browser agents stop; this one never signs in at all.
A sandboxed browser has to replay a login, and the sites worth automating are exactly the ones that fight that — device checks, second factors, session cookies tied to an address. Driving the browser you already have makes that whole class of failure disappear, and the trade is the plain one: the automation runs in your session, on your machine, with everything that session can already reach.
What it is
A browser-automation server that never launches a browser of its own. A local bridge connects your running Chrome to a relay over the DevTools Protocol, and the endpoint drives that session, so pages behind a login, a saved passkey or a device the site already trusts behave the way they do when you use them yourself. Navigation and clicks return a read of the page layout along with the action, and you can keep several named Chrome profiles connected at once — personal, work, social — addressing whichever one you mean on each call. The relay, bridge, web UI, agent packaging and deployment code are in the open repository; the page-extraction engine runs behind a documented boundary in a private one.
What you get
- Navigation, clicks, typing and JavaScript evaluation against the Chrome session you are already signed into
- A page-layout read returned with the navigation or click itself, plus targeted reads: visible text, a search for a phrase, or the element at a coordinate with its link, classes, text and aria attributes
- A fingerprint of an unfamiliar single-page app that ranks which extraction approach is likely to work on it
- A file set on a page's file input, for uploads that would otherwise need a hand on the keyboard
- Several Chrome profiles connected under one key, each with its own cookies, sessions and extensions, addressed by name
- A throwaway Chrome launched from a copy of one of your profiles for a sign-in flow, with its popup tabs discoverable and individually addressable, and a cleanup call when the flow is finished
Requirements
- Chrome on this computer, with the Unchained agent installed and running — it is what connects that Chrome to Unchained
- An Unchained account: the agent's first start signs you in through the browser and saves your key, UNCHAINED_API_KEY, in ~/unchained-agent/.env
- That key sent as a Bearer token in the Authorization header. Clients that cannot read environment variables need the key's value pasted into their config
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Reading a page that only exists behind your login
Navigate in the session you are already signed into and read the layout that comes back with the navigation, then pull the text or the element you want.
02
Getting through a sign-in flow that opens a popup
Launch a throwaway Chrome from a copy of one of your profiles, discover the tab the provider opened, act in it, and clean the instance up afterwards.
03
Keeping work and personal accounts apart in one run
List the connected profiles and address the one you mean by name, so a call meant for the work account never lands in the personal one.
04
Acting on a single-page app with no stable selectors
Find the target by coordinate and read its link, classes and aria attributes, then click it — or run the click through the page's own JavaScript when the widget will not take a coordinate.
05
Filling in a form that needs a file
Type the fields and set the file input directly, rather than handing the upload dialog back to a person.
11 tools
Listed in project docs. Your client may show a different list.
ddmcdp_clickcdp_typejs_evalcdp_set_filecdp_screenshotcdp_provision_launchlist_provisioned_tabscdp_provision_cleanuplist_connected_agentsBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- The Unchained agent running on this machine — it bridges your local Chrome and stores UNCHAINED_API_KEY in ~/unchained-agent/.env (its first start authorizes your Unchained account in the browser)
- UNCHAINED_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
curl -fsSL https://unchainedsky.com/install.sh | bash
export UNCHAINED_API_KEY="$(sed -n 's/^UNCHAINED_API_KEY=//p' "$HOME/unchained-agent/.env")"Hosted endpoint
ENDPOINT URL
https://api.unchainedsky.com/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add unchainedsky https://api.unchainedsky.com/mcp -t http -H "Authorization: Bearer $UNCHAINED_API_KEY"
