Language: English
Every MCP tutorial puts the server on a server. It doesn't have to be there.
If your app already holds the data, the auth, and the UI state, why copy all of it to a backend just so an agent can reach it? WebMCP lets your page expose its own tools to the agent directly, right where the user already is
In this hands-on workshop we'll build WebMCP tools from scratch in TypeScript and ship them inside a real web app. My production deployment is the reference case study: the architectural decisions, the gotchas, and the parts the docs don't cover yet.
You'll leave with working WebMCP tools, a clear sense of when browser-native beats server-side, and patterns you can deploy in your own app on Monday.