Fix gemini CLI extension

[shrey150]

• Swapped to a npx-based installation for the Gemini CLI extension MCP installation
• Renamed MCP to match convention (mcp-server-browserbase)

[greptile-apps]

Greptile Overview

Greptile Summary

Fixed Gemini CLI extension configuration by switching from local file execution to npx-based installation and renamed the MCP server key from browserbase to mcp-server-browserbase to match the project's naming convention.

• Replaced node ${extensionPath}/cli.js with npx @browserbasehq/mcp-server-browserbase for simpler, more reliable installation
• Updated server key to mcp-server-browserbase to align with package name @browserbasehq/mcp-server-browserbase
• Removed cwd parameter since it's no longer needed with npx-based execution

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The changes are minimal and improve the installation process by using npx instead of local file paths. The package name matches the published npm package, and the server key naming now follows the project's convention. No logical or functional issues detected.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
gemini-extension.json	5/5	Switched from local file execution to npx-based installation and renamed MCP server key to match naming convention

Sequence Diagram

sequenceDiagram
    participant User
    participant GeminiCLI as Gemini CLI Extension
    participant NPM as npm Registry
    participant MCP as MCP Server

    User->>GeminiCLI: Install extension
    GeminiCLI->>GeminiCLI: Read gemini-extension.json
    GeminiCLI->>NPM: npx @browserbasehq/mcp-server-browserbase
    NPM->>NPM: Download/use cached package
    NPM->>MCP: Execute mcp-server-browserbase
    MCP->>MCP: Start server with configured args
    MCP-->>GeminiCLI: Server ready
    GeminiCLI-->>User: Extension ready to use

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}