Publishes BrowserOS and neo’s external-agent MCP connection, with browser-specific Skills and client setup documentation.
The browseros-ai organization maintains BrowserOS, an agentic browser project. Its neo documentation describes a local MCP server for external tools, including coding agents, alongside the browser’s own interface.
BrowserOS brings agent tools into a browser product and exposes a neo MCP endpoint for external clients. The browser owns the page session; the connected agent issues tools and interprets their results. Connection checks should therefore establish both the selected browser context and a successful observation of the intended page.
Publisher identity, browser generation, and client configuration are separate facts. Use current neo documentation and official browseros-neo instructions together, and inspect the browser version before applying older extension tutorials.
First confirm access to the intended page and one permitted control action. Once both observations match the expected state, consider a task that uses an authenticated browser session.
Compare CitroLabs for task Spaces in a shared browser, Browser MCP for extension access to existing Chrome, Microsoft for Playwright MCP automation, Chrome DevTools for page diagnostics. Choose by the browser environment and task result you need.
A connection check should prove that the agent sees and can act on the intended page, rather than merely reporting that an endpoint was configured.
