The changes in the PR intercepts the name of the MCP client right after
server initialization, coverts it into one of the existing enum values,
and append it with the telemetry request.
Note that the client name is unset if there is no client connected yet.
This means the server_start event won't have a client name.
Tested with gemini-cli.
---------
Co-authored-by: Yulun Zeng <yulunz@chromium.org>
- `chrome-devtools-mcp.js` is the `npx chrome-devtools-mcp`
- `chrome-devtools.js` is the new CLI
- `-cli-options.js` is the corresponding options
- all these files are in the bin folder to indicate they are executable
I wanna test more NodeJS versions to see that this does not cause other
issues.
Deno test command:
```sh
npx @modelcontextprotocol/inspector deno --allow-env --allow-read ./build/src/index.js
```
Bun test command:
```sh
npx @modelcontextprotocol/inspector bun ./build/src/index.js
```
yulunz