It looks like MCP & browser use tools have emerged as two ways for LLMs to interact with their environment and perform tasks. From my perspective, they seem to serve overlapping purposes in a lot of ways (some MCP servers even let you control a browser directly). I'm trying to figure out which will become the dominant connectivity point for LLMs.
My gut reaction is MCP. Browser use tools seem like they'll be bottlenecked by well labeled GUI data and also in a future where we're predominantly building software to interact with other LLMs, why bother with a UI + backend endpoints when you can just neatly define the endpoints for LLM consumption?
Curious other folks thoughts on this. Maybe there's more of a middle ground than I'm making it out to be. Thanks!
playwright vs browsertools vs puppeteer
MCP vs browser use - which will win out?
Did you know that Claude Code can use the browser to QA its own work?
Claude code + playwright mcp - how did you speed up the browser interactions
Videos
» npm install @playwright/mcp
which of these mcp servers is best be able to connect my cursor to see the error and issues my card is dealing with? or another option?