they can also call an api right? like just add some docs they can read to k ow what routes are what and thats it? like i dont understand why they need a special api to interact with an api??
calling an api is backend integration but webmcp solves a different problem.
most websites don't have a public api. even when they do, apis require server-side implementation, auth, rate limiting, and maintenance.
webmcp lets a site expose its existing frontend js functions as tools, no server needed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
they can also call an api right? like just add some docs they can read to k ow what routes are what and thats it? like i dont understand why they need a special api to interact with an api??
calling an api is backend integration but webmcp solves a different problem.
most websites don't have a public api. even when they do, apis require server-side implementation, auth, rate limiting, and maintenance.
webmcp lets a site expose its existing frontend js functions as tools, no server needed.