This directory contains extensions / MCP (model context protocol) server configurations useful for Chromium development. Each subdirectory within this directory corresponds to one extension.
Configuration are provided in gemini-cli extensions format.
Use agents/extensions/install.py to manage extensions. This script is a wrapper around the gemini extensions commands.
If you have previously installed extensions at the project-level, you will be prompted to run the fix command to migrate them to the new user-level model:
vpython3 agents/extensions/install.py fix
To see a list of available extensions and their install status:
vpython3 agents/extensions/install.py list
By default, extensions are installed as links in your user-level extension directory (~/.gemini/extensions).
vpython3 agents/extensions/install.py add <extension_name_1> <extension_name_2>
To copy the extension directory instead of creating a link, use the --copy flag:
vpython3 agents/extensions/install.py add --copy <extension_name_1>
vpython3 agents/extensions/install.py update <extension_name>
You can also update all installed extensions at once:
vpython3 agents/extensions/install.py update
vpython3 agents/extensions/install.py remove <extension_name>
There are three types of MCP server configurations supported:
Local MCP Server (chromium tree): The configuration for these servers points to a local MCP server that is located elsewhere within the Chromium source tree.
Local MCP Server (prebuilt): These servers are prebuilt as CIPD packages and located within the same subdirectory as their configuration files.
Remote MCP Server: The configuration for these servers contains a reference to a remote URL where the MCP server is hosted.
See the example server for a minimal example for creating an MCP tool with python and FastMCP