DeepSeek browser testing with claude-cli and chrome-devtools-mcp

Recently I installed claude code – without an Anthropic account. I am using DeepSeek api because it’s good, and cheap.

For website updates, it is helpful to have the AI automate some things, to check that the updates work irl. Recently Google launched their official Crome Devtools MCP. I heard it works great with claude cli. Turns out it works great with claude cli hacked to use DeepSeek api also!

Installation

(After installing and setting up claude-code-router and claude cli)

Just run: claude mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Now you can run the claude-code-router in your coding project directory:

ccr code

and then type /mcp to check – the devtools should be listed.

Running

You can do this in several ways, but I like to run the browser and get the mcp to connect to already running session. On my Arch linux laptop I do this:

google-chrome-stable --remote-debugging-port=9222 --user-data-dir=/home/tom/Downloads/temp_chrome/

You need to specify the default debug port and a directory for your session (if you don’t add a temp directory, the AI might have access to your Chrome session, logins etc. Maybe you want that?). Chrome will think you are starting it for the first time – at least the first time you do this – so click through the prompts.

After Chrome is running, you can ask claude cli (with DeepSeek api back-end) to do stuff in your browser. Just ask it to use chrome-devtools-mcp and it will.

I am hoping to use this a lot, make changes and then get the AI to test everything works, iterate..

Don’t do this

ccr code --dangerously-skip-permissions

– gives the ai full control of your computer and no need to ask permission from you to do whatever it wants. Including finishing your project while you watch anime! (Or deleting everything on your hard drive…).

Leave a Reply

Your email address will not be published. Required fields are marked *