Free tools Windows power users keep installed
One-click scans. No signup required.
To run Agent Infra’s browser server locally, install Node.js 18 or newer, choose an MCP-compatible client, and add @agent-infra/mcp-server-browser@latest as a stdio server launched by npx. This is the simplest starting point: it avoids exposing a network endpoint and lets the MCP client start the browser server when needed. Remote operation is also documented, but the README’s example URLs appear malformed, so verify the current endpoint format before configuring a remote client.
What the server does
Agent Infra’s @agent-infra/mcp-server-browser package connects an MCP client to browser automation tools. Its package README describes it as a browser automation server based on Puppeteer’s structured accessibility data, with optional vision support for complex visual layouts. The README also describes support for local or remote browsers and a custom browser engine; these are project capabilities, not independent performance claims. See the package README and npm listing for the package’s own setup notes.
The practical distinction is that structured accessibility data gives an agent page information to work with, while vision mode is available when a task depends on visual layout or details that the structured path does not handle well. The README does not establish that one mode is universally faster or more accurate, so choose based on the page and task rather than assuming vision is an automatic upgrade.
Prerequisites
- Node.js 18 or newer. The package listing specifies this minimum runtime.
- An MCP client. The README names VS Code, Cursor, Windsurf, and Claude Desktop as examples; other clients that support MCP may also work.
- A browser configuration suited to your environment. Local defaults are the least complicated. If you need a particular browser executable, browser channel, proxy, viewport, or profile, configure those options deliberately rather than assuming the default machine setup will match.
Package release information is time-sensitive. The npm listing captured for this article identified version 1.2.29 and said it had last been published nine months before that listing was captured; that does not establish the latest version today. The commands below use the README’s @latest tag so npm resolves the current tagged release when you run them.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
Set up a local stdio server
For local use, the MCP client launches the server process directly. Add this entry to the client’s MCP configuration, preserving any other existing server entries in the same mcpServers object:
{
"mcpServers": {
"browser": {
"command": "npx",
"args": ["@agent-infra/mcp-server-browser@latest"]
}
}
}The key name browser is a label for the server in the client configuration; it is not a required package name. The command and argument tell the client to invoke npx and run the package. The first launch may need to retrieve the package, so the machine needs npm registry access at that point. Do not replace or discard the rest of your client’s MCP settings when adding this entry.
VS Code
The package README documents a CLI route that adds the server:
code --add-mcp '{"name":"browser","command":"npx","args":["@agent-infra/mcp-server-browser@latest"]}'Alternatively, use the JSON configuration shape above in the MCP configuration location supported by your VS Code version. Client interfaces and configuration conventions can change; if the command is unavailable in your installation, use the client’s current MCP setup workflow rather than treating the CLI example as universal.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Cursor
The README’s route is Cursor Settings → MCP → Add new MCP Server. Add a command-type server with npx @agent-infra/mcp-server-browser, or use the equivalent JSON configuration. To track the current npm release at launch, use the explicit argument @agent-infra/mcp-server-browser@latest as in the shared configuration above.
Claude Desktop and Windsurf
For Claude Desktop, the package README shows the same mcpServers JSON pattern. Windsurf users are directed to that client’s MCP documentation; the exact interface is client-version dependent. In either case, configure the server as a local command using npx, then restart or refresh the client if it does not load the new server configuration.
Check that the client can use it
After saving the configuration, use the client’s MCP server status or tool interface to check whether the server started and its browser tools are available. The package README lists tools for navigation, clicking, filling forms, evaluating page JavaScript, taking screenshots, managing tabs, and closing the browser. It also lists resources such as console logs, downloads, and screenshots. The listing captured for this article provides only a partial tool table, so treat those as examples rather than a complete inventory of the API.
Start with a low-risk page and a simple navigation or screenshot task. Then try interaction steps such as clicking or filling a form. Be explicit with the agent about the page and action you want; as with other browser automation, an agent’s ability to interpret a page does not guarantee it will choose the right control or produce the intended result. Avoid submitting real transactions or changing important account settings during initial validation.
Recommended Free Tools
Rank #3
- Include: 1x serverbook(not include guest check)
- Design: Unique design deluxe and durable server book to let your outstanding.Fit Server Apron well.
- Function: Have 8 slot.One slot for checkbook,3 slots for cards,3 slots receipt or money or other daily food special.also a slot for pen
- Size: 7.6x4.9x0.78inch,6oz
- Material: Made with high quality PU leather
Choose browser and runtime options
The README documents command-line options covering several parts of browser operation. Exact option spellings and accepted values can vary by release, so consult the package README for the current invocation syntax before copying flags into a production configuration.
| Setting area | What it controls | When to consider it |
|---|---|---|
| Browser channel or engine | Selection among Chrome, Edge, or Firefox, and support for a custom browser engine | When the default browser is unavailable or a task depends on a particular browser. |
| Connection endpoint | CDP or WebSocket connection details | When connecting to a browser process that is already running or managed elsewhere. |
| Executable and display | Browser executable path and headless mode | When the browser is installed in a nonstandard location or the environment has no desktop session. |
| Network | Proxy server and proxy bypass settings | When the browser must reach sites through an organization’s proxy or bypass it for specified hosts. |
| Identity and session | User agent and user data directory | When a task needs a particular browser identity or persistent browser profile. Treat profile data as sensitive. |
| Rendering and output | Viewport size and output directory | When the page must render at a defined size or captures need a known destination. |
| Interpretation | Optional vision mode | When a visual layout is important or structured page information is insufficient for the task. |
The README also documents runtime HTTP headers for viewport size (x-viewport-size), vision coordinate factors (x-vision-factors), and user agent (x-user-agent), and says header names are case-insensitive. These are request-time controls in the documented setup; they are not substitutes for every command-line option. If you change viewport dimensions while using vision coordinates, ensure the coordinate factors match the rendered view, or visual targeting can be misaligned.
Run remotely only after verifying the endpoint
The README says to start a remote server with --port <port> and illustrates port 8089. It describes Streamable HTTP at /mcp and SSE at /sse, recommending Streamable HTTP. However, the displayed examples use http://127.0.0.1::8089/mcp and http://127.0.0.1::8089/sse, each with two colons before the port. Those strings are malformed as ordinary host-and-port URLs; do not paste them as working addresses. Check the package’s current release documentation or repository for the intended endpoint format before configuring a client.
For a remote MCP client, the README describes URL-based setup and an optional type: "streamable-http" setting where the client supports it. The details depend on the corrected endpoint and the client’s transport support, neither of which should be inferred from the malformed examples. A remote endpoint also changes the operational boundary: instead of starting a local process, the client connects over the network, so deployment and access controls need to match your environment.
Virtual displays and in-memory use
For a VNC or virtual-display environment, the README shows starting with DISPLAY=:0. Use that only when it corresponds to the display configured on your host; it is not a universal value for all Linux or container setups.
JavaScript and TypeScript applications can also use the server in memory through the Model Context Protocol SDK and InMemoryTransport, according to the README. This route avoids requiring end users to install and launch the CLI, but it is a different integration from the JSON stdio configuration and requires the application to manage the MCP connection itself.
Security and reliability considerations
- Keep local setup local where possible. Stdio is a straightforward choice when the MCP client and browser run on the same machine and there is no need to expose a network service.
- Be careful with persistent profiles. A user data directory may contain session information. Do not point an agent at a personal profile unless you intend to give it access to that browser state.
- Separate Chrome DevTools MCP from this package. Chrome documents a distinct DevTools MCP setup that can connect to an existing Chrome session. Chrome warns that such a session gives the agent access to logged-in accounts, cookies, and other data. That warning applies to Chrome’s existing-session setup; it should not be read as a claim that Agent Infra uses the same connection behavior. See Chrome’s DevTools configuration documentation.
- Plan for page variability. A site can change its layout, require authentication, block automation, or load content asynchronously. Give the agent enough task context to handle expected variations, and verify consequential actions yourself.
- Do not assume a benchmark or service guarantee. The package material cited here does not establish independent speed, success-rate, or uptime figures.
Troubleshooting common setup problems
| Symptom | Likely cause | What to check or change |
|---|---|---|
| The MCP client does not show the server | Invalid JSON, configuration saved to the wrong client location, or client has not reloaded its settings. | Validate the JSON structure, confirm the entry is nested under mcpServers where required, and restart or refresh the MCP client. |
| Server launch fails immediately | Node.js is older than the stated minimum, npx is unavailable, or npm cannot obtain the package. |
Check that Node.js is version 18 or newer, ensure npx is on the executable path, and check network or registry access. |
| Browser does not launch | Browser channel or executable path is wrong, required browser is not installed, or the environment lacks a usable display. | Review the selected browser and executable settings; use headless operation where appropriate, or configure the correct display for a virtual-display environment. |
| Page is the wrong size or vision clicks miss | Viewport and vision coordinate factors do not match the rendered dimensions. | Set the viewport intentionally and align x-vision-factors with the vision coordinate system described by the current package documentation. |
| Remote connection URL is rejected | The copied README examples contain an extra colon before port 8089. | Do not use the malformed examples as-is. Verify the intended host, port, and transport path in current package documentation before connecting. |
| Page access differs behind a proxy | The browser’s traffic is not using the expected proxy or bypass list. | Check the proxy server and bypass configuration for the browser process, not only the MCP client’s network settings. |
| Agent cannot interpret a particular control | The control may not be represented adequately in structured accessibility information, or visual details may matter. | Try the package’s optional vision mode for that task and provide a precise instruction; confirm the selected control before any consequential action. |
Or skip the browser setup
If your job is to capture a website rather than let an agent freely interact with a browser, ScreenshotNeo offers a one-request screenshot API and an MCP server for AI agents. For a PNG, JPEG, WebP, or PDF capture, the cURL example below saves a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL with the page you need and supply your API key. The same endpoint can be called from Python or Node.js; see the ScreenshotNeo documentation for options and response details.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- 【Perfectly Fit in Server Aprons】: Our black server book size is 8.15" x 5.12" x 0.59", which can hold a regular guest checkbook and is handy to be carried in a server apron pocket, won’t be too tight or too big, efficiency as a server money holder.
- 【Stay Organized All in Needs】: 9 compartments and 1 pen holder in one serving book, with a zipper pocket to store your coins, changes, and money. Multi-functional pockets to organize checkbooks, cash, ticket books, server pads, credit cards, coupons, or any other paper documents, nice waitress accessories partner for servers.
- 【Waterproof Leather Material】: The waitress book is made of premium sturdy PU leather, Eco-friendly and odorless, features excellent workmanship and tight stitching, easy to clean. Plus an elastic pen loop to be a nice waitstaff organizer to help you hold the pen that is always away from home and improve the service speed.
- 【Portable and Long-lasting】: Our server books for the waiter are lightweight to carry around, and sturdy as a guest checkbook holder, premium material makes them sturdy and won’t easily deform or press the belly when bent over.
- 【100% Satisfaction Guarantee】: We hope you love your server book wallet and place your order with confidence, all of our men’s & women’s server books are backed by a replacement guarantee. Any questions will be answered within 24 hours.
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo removes cookie or consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers indicate the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to try up to 1,000 screenshots per month with no card.
Frequently Asked Questions
Can I use this server with an MCP client other than the ones named in the README?
The package listing says other MCP clients are possible; whether setup works depends on that client’s supported MCP transport and configuration format.
Does the package provide a complete list of every browser tool?
The package listing available here shows only a partial tool table, so consult its current README for the complete tool inventory.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
