Post

WebMCP is an amazing way to AI enable your web app. And the declarative API makes it easier than ever. So why isn't WebMCP taking off the way that MCP did? youtu.be/ivHYOwMRayc

youtu.beWebMCP: 50% PerfectYouTube video by Jack Herrington

Doug Parker

@develwithoutacause.dwac.dev

15 June

💯 I've had similar conversations with Chrome that it's hard to "sell" WebMCP without a way to actually demo the consumer UX of the feature. DevTools are great, but not sufficient to get apps involved in this.

Doug Parker

@develwithoutacause.dwac.dev

15 June

Since you mentioned the declarative API and ICYMI, #Angular has an experimental integration which improves on the declarative API to better support dynamic forms and propagate submission completion timing and error messages back to the agent. angular.dev/ai/webmcp

angular.devWebMCP • AngularThe web development framework for building modern apps.

Doug Parker

@develwithoutacause.dwac.dev

Still early, but hoping to create a developer experience where it is as easy as possible to add WebMCP support to a form, yet create better tools than the spec could on its own.

15/6/26, 6:08 pm0 reposts0 likes

Latch

@latch-tools.bsky.social

17 June

Nice — same space we hit building Latch. What bit us: declarative <form data-mcp-tool> is great for inputs, but agents also need a structured result/error schema back, plus a polyfill so non-Chrome agent browsers can call it now. Are you handling the return contract, or the form's success page?