Hosted vs self-run: Browser Automation

This page compares a hosting model, not a tool-for-tool match: WingMan's own hosted Browser Automation tools (called over one shared MCP endpoint, metered per call) against third-party MCP servers in the same category that you install and run yourself. No server here is claimed to be equivalent to a specific WingMan tool - the comparison is setup and hosting model, drawn straight from each side's registry entry.

WingMan hosted

Tool	Price	Category
Browse	Metered - see /pricing	browser
Browse Back	Metered - see /pricing	browser
Browse Click	Metered - see /pricing	browser
Browse Close	Metered - see /pricing	browser
Browse Discover	Metered - see /pricing	browser
Browse Evaluate	Metered - see /pricing	browser
Browse Extract	Metered - see /pricing	browser
Browse Fill	Metered - see /pricing	browser
Browse Links	Metered - see /pricing	browser
Browse Navigate	Metered - see /pricing	browser

+8 more in this category - see the full hosted tools hub.

Self-run (third-party)

Server	Transport	What running it means	Install method
ai.foura/mcp	`http`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)

When to choose which

Choose the WingMan hosted tool(s) when

No install and no runtime to manage - call it over the same MCP endpoint as every other WingMan tool (POST https://wingmanprotocol.com/mcp).
One account and one key cover every hosted tool in every category.
Metered per call via x402 (USDC on Base), or included in the free-tier quota - see /pricing.

Choose a self-run server when

Full control over the server's own account, data residency, and configuration.
Useful when the specific vendor integration you need is not one WingMan hosts.
You handle install yourself - a local runtime (npx/uvx/Docker) for stdio servers, or the vendor's own account and auth for remote (http/sse) ones.