Polish readme

* add configuration section
* move user-data-dir to new concepts section

Author: sebastianbenz

README.md

@@ -8,7 +8,7 @@ prototype!
 
 `chrome-devtools-mcp` exposes content of the browser instance to the MCP clients
 allowing them to inspect, debug, and modify any data in the browser or DevTools.
-Avoid sharing sensitive or personal information that you do want to share with
+Avoid sharing sensitive or personal information that you don't want to share with
 MCP clients.
 
 ## Requirements
@@ -33,7 +33,7 @@ Add the following config to your MCP client:
 ```
 
 > [!NOTE]  
-> `Using `chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
+> Using `chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
 
 ### MCP Client specific configuration
 
@@ -119,7 +119,8 @@ claude mcp add chrome-devtools-mcp npx chrome-devtools-mcp@latest
 
 ## Configuration
 
-For example, to launch the system-installed Chrome Canary pass `--channel=canary` as an argument:
+The Chrome DevTools MCP server supports the following configuration option. Pass them via the `args` property
+in the JSON configuration. For example:
 
 ```json
 {
@@ -128,20 +129,22 @@ For example, to launch the system-installed Chrome Canary pass `--channel=canary
       "command": "npx",
       "args": [
         "chrome-devtools-mcp@latest"
+        "--browserUrl=http://localhost:8080",
         "--channel=canary",
+        "--headless=true",
+        "--isolated=true",
       ]
     }
   }
 }
 ```
 
-### User data directory
+The following options are supported when running the Chrome DevTools MCP server from an MCP client:
 
-`chrome-devtools-mcp` starts a Chrome's stable channel instance using the user
-data directory at `$HOME/.cache/chrome-devtools-mcp/mcp-profile-$CHANNEL` on
-Linux/MacOS and `%HOMEPATH%/.cache/chrome-devtools-mcp/mcp-profile-$CHANNEL` in
-Windows. The user data directory is not cleared between runs and shared across
-all instances of `chrome-devtools-mcp`.
+* **browserUrl**: Connect to a running Chrome instance using [port forwarding](https://developer.chrome.com/docs/devtools/remote-debugging/local-server). 
+* **channel**: By default the Chrome MCP Server will run the stable version of Chrome. Use this option to use the `canary`, `beta` or `dev` channel version instead.
+* **headless**: Set to `true` if the browser should be run in headless mode without UI. The default is `false`.
+* **isolated**: Set to `true` if you want to always start the browser with a clean user profile in a temporary `user-data-dir`. The directory will be cleaned up when closing the browser. The default is `false`. See the [user data directory section](#user-data-directory) for more details.
 
 ## CLI
 
@@ -174,3 +177,19 @@ Examples:
 ```
 
 <!-- END AUTO GENERATED CLI -->
+
+## Concepts
+
+### User data directory
+
+`chrome-devtools-mcp` starts a Chrome's stable channel instance using the following user
+data directory:
+
+* Linux / MacOS: `$HOME/.cache/chrome-devtools-mcp/mcp-profile-$CHANNEL`
+* Window: `%HOMEPATH%/.cache/chrome-devtools-mcp/mcp-profile-$CHANNEL`
+
+The user data directory is not cleared between runs and shared across
+all instances of `chrome-devtools-mcp`. Set the `isolated` option to `true`
+to use a temporary user data dir instead which will be cleared automatically after
+the browser is closed.
+