Legba MCP server for Windsurf
Connect Cascade to Legba's disposable browser. One user-level config makes the server available across your Windsurf workspaces.
Browser control from Cascade.
Cascade can request a fresh Chromium session, navigate it, interact with the page, extract rendered content, and take screenshots. Legba supplies a residential IP and fresh fingerprint for that session. The destroy tool removes browser state when Cascade completes the task.
Update the Cascade config.
Open ~/.codeium/windsurf/mcp_config.json. You can reach the same file from Settings, then Cascade, then MCP servers. Add the legba entry inside the existing mcpServers object if other servers are already present.
Windsurf reads this file at the user level, so one entry serves every workspace. The server runs through npx and receives LEGBA_API_KEY from its env block. Preserve other MCP entries and review the command before enabling the new tools in Cascade.
{
"mcpServers": {
"legba": {
"command": "npx",
"args": ["-y", "legba-browser-mcp"],
"env": {
"LEGBA_API_KEY": "lgb_your_api_key"
}
}
}
}Replace the placeholder with your Legba API key. Save the file, then refresh the MCP list or restart Windsurf. The config launches the same npx package as the main MCP guide.
Check the Cascade tool list.
- Open the MCPs control in Cascade. Select
legbaand confirm the server has connected without a startup error. - Review its enabled tools. Cascade should list
session.spawn,navigate,extract,act,screenshot, andsession.destroy. - Ask Cascade to create a session and open a test URL. Confirm the tool returns a session ID and page output. Destroy the session when the check finishes.
If Cascade shows the server without tools, reopen the MCP settings and inspect its connection state. Check the JSON object name and API key value. Refresh the list after every correction so Cascade restarts the stdio process.
Continue with the docs, API quickstart, or cloud API pricing.
Also installing for: Cursor, Claude Code, Claude Desktop, and VS Code.