Windows-MCP

Puppeteer Real Browser MCP Server starts and owns a local Chrome process for an MCP client, exposing navigation, content reading, element lookup, clicks, typing, waits, and scrolling. It defaults to a visible browser, supports headless mode, proxies, custom Chrome paths, and dedicated profiles, and closes only the process it launched. The workflow requires reading page content before interaction, allows one browser session, and does not provide a real CAPTCHA solver.

AutoGPT’s current platform uses a low-code block builder to create agents and workflows, manage deployments, and run automations continuously from external triggers. The repository also retains classic tooling such as Forge and an agent benchmark. Self-hosting is a technical Docker-based setup, the hosted service remains a closed beta, and licensing differs between the Polyform Shield platform directory and the MIT-licensed classic components.

agent-browser gives AI agents commands to open pages, capture accessibility snapshots, click or fill referenced elements, read text, take screenshots, and manage tabs. Its native Rust CLI can also run as an MCP server with selectable tool profiles. Chrome must be installed or downloaded for automation, while features such as the encrypted authentication vault are opt-in.

Use one CLI to find, install, update, or remove skills across Claude Code, Codex, Cursor, OpenCode, and many other agents. It can also generate a selected skill prompt or launch a supported agent without installing the skill into an agent directory. Sources can come from GitHub, GitLab, generic Git URLs, or local paths, with project or global installation; support for advanced fields still varies by agent.