Julia Rapczynska

Today, most browser agents use the web almost like humans do: inspect the DOM, accessibility tree or pixels, find the right element, click it, and hope the interface has not changed.
But why are we teaching machines to reverse-engineer interfaces that we built ourselves?
WebMCP explores a different model. A webpage can expose structured capabilities directly to an agent through document.modelContext: named tools, input schemas and JavaScript execution callbacks. Instead of figuring out which button means “add this session”, an agent can invoke the underlying addSession() operation directly.
In this talk, we’ll look at what WebMCP actually changes in web application architecture, why it is not simply MCP running inside the browser, and how a single domain operation can power both the human UI and the agent-facing interface.
We’ll also look at the less comfortable part: giving an agent structured tools does not make it trustworthy. Authenticated browser sessions, authorization boundaries, tool output and prompt injection still matter.
The interesting shift is not that AI can finally click our websites better.
It’s that clicking may no longer be the web application’s only machine-readable interface.

As a Full Stack Engineer with a strong focus on Angular, TypeScript, Nx, and Design Systems, I work on the architecture behind scalable UI platforms: reusable foundations, federated frontend infrastructure, automation, documentation, and developer tooling that help large teams move faster without losing consistency.
A big part of my current work is exploring how AI can support engineering in a practical, responsible way. I’m interested in how LLM-supported workflows, structured knowledge systems, and internal “second brain” approaches can help developers understand complex codebases, make better decisions, and reduce the friction of working at scale.
I’m an outgoing community person who enjoys turning real engineering challenges into talks, workshops, and discussions. I like sharing not only the final solution, but also the messy path behind it: the trade-offs, failed attempts, migration stories, architecture debates, and lessons that are usually the most useful for other developers.