chrome-devtools
Connects to Chrome over the DevTools Protocol to inspect the DOM, network requests and console output.
1,020 MCP servers in 588 plugins. Gemini CLI runs MCP servers from settings.json.
Gemini CLI runs MCP servers from its own config file. Open a server below, follow the link to its repository and add the entry there to the file.
Copy each server's entry from its repository. Flowy has not tested these in Gemini CLI.
Connects to Chrome over the DevTools Protocol to inspect the DOM, network requests and console output.
Pulls shadcn/ui component source so the agent can add and adapt them in place.
Drives a real browser so the agent can open pages, click, fill forms and read what actually rendered.
Queries a Supabase project: Postgres tables, auth users, storage and edge functions.
Coordinates swarms of AI agents and orchestrates multi step automated development workflows and task pipelines.
Develops and visually tests UI components in isolation outside of the full application.
Gemini CLI runs MCP servers, and it keeps them in settings.json. A Claude Code plugin starts its servers through Claude Code, so for Gemini CLI you copy each server's entry from its repository. Flowy has not tested these in Gemini CLI.
Gemini CLI reads its MCP servers from settings.json. You can also add one from the command line with gemini mcp add, using the command the server's repository documents.
Open the server's listing, follow the link to its repository and copy the server's entry into settings.json. Flowy lists the server and the plugin it ships in. It does not print the entry.
By the GitHub stars of the plugin each server ships in. Flowy reads each plugin from its public repository and does not host, audit or certify servers, so check what a server runs before you add it to Gemini CLI.
Looking for the Claude Code version? MCP Marketplace for Claude Code