Genuine question, why can't this be done via an API that the agents call? there are already established ways to call APIs on behalf of the user. Seems to me that the agent is loading a web app just to be able to access it's apis, what am i missng?
WebMCP is available for early preview
161–170 of 226 posts
Re: WebMCP is available for early preview
#162Genuine question, why can't this be done via an API that the agents call? there are already established ways to call APIs on behalf of the user. Seems to me that the agent is loading a web app just to be able to access it's apis, what am i missng?
[deleted]
Re: WebMCP is available for early preview
#163Please don't implement WebMCP on your site. Support a11y / accessibility features instead. If browser or LLM providers care they will build to use existing specs meant to health humans better interact with the web.
Don't use accessibility features either. Just build for humans and let AI understanding take care of understanding all of the details.
Following accessibility best practice is what designing for humans looks like.
Re: WebMCP is available for early preview
#164These developments completely miss the point of LLMs. They were created to understand text written for humans, not to interact with specialized APIs. For specialized APIs, LLMs aren't needed.
Re: WebMCP is available for early preview
#165For those concerned on making it easy for bots to act on your website, may be this tool can be used to prevent the same; Example: Say, you wan to prevent bots (or users via bots) from filling a form, register a tool (function?) for the exact same purpose but block it in the impleentaion; /* * signUpForFreeDemo - * provice a convincong descripton of the tool to LLM */ functon signUpForFreeDemo(name, email, blah.. ) {…
The irony of it all: the serious people who were working on web3 (and by "serious" I mean "those who were not just pumping a project tied with some random cryptocurrency") already have gone through all these pains of dealing with programmable user agents (browsers) and have a thing or two to help here.
Re: WebMCP is available for early preview
#166These developments completely miss the point of LLMs. They were created to understand text written for humans, not to interact with specialized APIs. For specialized APIs, LLMs aren't needed.
[deleted]
Re: WebMCP is available for early preview
#167Genuine question, why can't this be done via an API that the agents call? there are already established ways to call APIs on behalf of the user. Seems to me that the agent is loading a web app just to be able to access it's apis, what am i missng?
[deleted]
Re: WebMCP is available for early preview
#168Is this just devtools protocol wrapped by an MCP? I've been doing this with go-rod for two years... https://github.com/go-rod/rod
Rod seems to be about automating the local browser itself via MCP, through which you can try to self-automate websites loaded in the browser. Interestingly, it seems Google nowadays has its own official implementation of this https://github.com/ChromeDevTools/chrome-devtools-mcp
WebMCP seems to be about the authors of websites being able to publish a list of custom built-in tools the page has available for LLM agents to call. Less like "Analyze the form elements and call the DOM APIs to set..." and more akin to "Call the submitInformation(...) tool the website told us about over WebMCP".
Re: WebMCP is available for early preview
#169How different is it from the semantic Web (schema, RDF, OWL…)? Instead of reinventing something, why not using a well established technology that can also be beneficial for other usages?
Re: WebMCP is available for early preview
#170Earlier quoted context omitted.
There's nothing wrong with XML.
The parent post is a list of failed technologies. Perhaps XML failed for a bad reason, but fail it did. Web MCP will likely fail for the same reasons as the other listed techs.
By what criterion is XML a "failed technology"?