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. Windsurf runs MCP servers from mcp_config.json.
Windsurf 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 Windsurf.
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.
Windsurf runs MCP servers, and it keeps them in mcp_config.json. A Claude Code plugin starts its servers through Claude Code, so for Windsurf you copy each server's entry from its repository. Flowy has not tested these in Windsurf.
Windsurf reads its MCP servers from mcp_config.json. Add the entry from the server's repository to that file.
Open the server's listing, follow the link to its repository and copy the server's entry into mcp_config.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 Windsurf.
Looking for the Claude Code version? MCP Marketplace for Claude Code