DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to drive an existing anti-detect browser window over CDP with Nuphus MCP

Attach the server to a fingerprint browser you already run, with optional port self-healing on reopen.

Authorization notice. Nuphus MCP is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Account pooling. Running many accounts through anti-detect browsers can break site terms of service, and the README does not address this, so check the rules of each site first.

Who it is forA team member who already runs an anti-detect browser and wants an agent to operate inside one of its windows.

The problemFingerprint browsers often change debug ports when a window reopens, which breaks a fixed connection URL.

The outcomeThe agent attaches to the external browser through CDP and runs browser_* tools in that window, without launching a managed Chrome.

What you need first

  • Rust stable toolchain to build from source with Cargo
  • Chrome or Edge installed for browser tools
  • An MCP client that supports stdio servers
  • Windows for full desktop control; macOS needs the Accessibility permission
  • Your own vision model API key only if you use desktop_vision

Steps

  1. Start your fingerprint browser with a debugging port: chrome --remote-debugging-port=9222 --user-data-dir=...
  2. In the MCP client env, set NUPHUS_MCP_BROWSER_CDP_URL to http://127.0.0.1:9222.
  3. (optional) Set NUPHUS_BROWSER_EXE_PATH and NUPHUS_BROWSER_USER_DATA_DIR so the server can re-resolve the port after a window reopens.
  4. Call a browser_* tool from the agent and confirm it attaches to the external window.

Prompt for your agent

Use the nuphus-mcp server to attach to the external browser at http://127.0.0.1:9222 and take a browser snapshot of the current page. Return the page title and the first five interactive elements. Verify the snapshot comes from the attached window and not a managed Chrome.

Caveat. If the external endpoint stops answering and no browser identity is set, attach failures are hard errors, and the server never falls back to a managed Chrome or kills your browser.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page