> If I asked you to build a table and gave you a Home Depot you probably would have a harder time than if I gave you a saw, a hammer and some nails. I doubt that, first and not least because Home Depot stocks lumber.
MCP-B: A Protocol for AI Browser Automation
81–90 of 200 posts
Re: MCP-B: A Protocol for AI Browser Automation
#82This puts the burden on the website owner. If I go through the trouble of creating and publishing an MCP server for my website, I assume that through some directory or method I'll be able to communicate that with consumers (browsers & other clients). It would be much more valuable for website owners if you can automate the MCP creation & maintenance.
Pretty much every revolution in how we do things originates from the supplier. When websites became a thing the burden was on businesses to build them. Same with REST APIs. Same with mobile apps. As soon as there’s a competitive advantage to having the new thing, companies will respond if consumers demand it.
Re: MCP-B: A Protocol for AI Browser Automation
#83can someone explain like I am five?
Example:
1. An author has a website for their self-published book. It currently checks book availability with their database when add to cart is clicked.
2. The website publishes "check book availability" and "add to cart" as "tools", using this MCP-B protocol.
3. A user instructs ChatGPT or some AI agent to "Buy 3 copies of author's book from https://theirbooksite"
4. The AI agent visits the site. Finds that it's MCP-B compliant. Using MCP-B, it gets the list of available tools. It finds a tool called "check book availability", and uses it to figure out if ordering 3 copies is possible. If yes, it'll next call "add to cart" tool on the website.
The website here is actively cooperating with the agent/LLM and supplying structured data. Instead of being a passive collection of UI elements that AI chatbots have to figure out based on UI layouts or UI captions, which are generally very brittle approaches.
Re: MCP-B: A Protocol for AI Browser Automation
#84Would it be possible to do this with any arbitrary website since we can execute JS client side?
Re: MCP-B: A Protocol for AI Browser Automation
#85But any accessibility tool will be exploited by nefarious actors so I wonder how many main stream websites/apps would implement these MCP.
Has anyone tried any MCP for improving accessibility?
Re: MCP-B: A Protocol for AI Browser Automation
#86Sounds like a very strange world of robots fighting robots
Re: MCP-B: A Protocol for AI Browser Automation
#87Could all of this be replaced simply by publishing OpenAPI (Swagger) spec and using universal swagger mcp client ??? This basically leaves up to the user to establish authenticated session manually. Assuming claude is smart enough to pick up API key from prompt/config, and can use swagger based api client, wouldnt that be the same?
Re: MCP-B: A Protocol for AI Browser Automation
#88Could all of this be replaced simply by publishing OpenAPI (Swagger) spec and using universal swagger mcp client ??? This basically leaves up to the user to establish authenticated session manually. Assuming claude is smart enough to pick up API key from prompt/config, and can use swagger based api client, wouldnt that be the same?
pls don't put an api key in a prompt
Re: MCP-B: A Protocol for AI Browser Automation
#89This MCP stuff is leading dev down the wrong path. We should be focusing on llms using self discovery to figure out information.
I had that opinion too. You can ask an agent to browse a web page and click a button etc. They will work out how to use a browser automation library. But it’s not worth the cost, time spent waiting or the inconsistency between implementations. MCP just offloads that overload, much like how they can use bash tools when they are quite capable of writing an implementation of grep etc.