Alexandra Klepper

Alexandra Klepper authors Chrome for Developers guidance for WebMCP, including the overview, API explanations, implementation practices and workflow design material.

Original profile or publication ↗

Authorship comes from Chrome for Developers page metadata; portrait comes from the linked public GitHub profile. Checked September 19, 2026.

Referenced in 101

1. WebMCP 101

   WebMCP overview ↗

   Chrome frames WebMCP as structured page actions that complement the DOM rather than asking an agent to infer every interaction from pixels and markup.

2. WebMCP 101

   When to use WebMCP and MCP ↗

   WebMCP is ephemeral and bound to a live page; MCP is a persistent service connection. Many serious products need both layers.

3. WebMCP 101

   WebMCP imperative API ↗

   The imperative API is the flexible path for dynamic tools whose schemas, availability and execution depend on live application state.

4. WebMCP 101

   WebMCP declarative API ↗

   Semantic HTML forms can become agent tools without moving the workflow out of the visible, accessible interface.

5. WebMCP 101

   WebMCP best practices ↗

   Expose a small set of distinct, goal-shaped tools with strict validation, useful errors and evals; do not mirror every UI control.

6. WebMCP 101

   Build your user's agentic workflows with WebMCP tools ↗

   Design from the user's end goal and initial state, role-play likely tool sequences, then test variance and recovery before publishing a tool.

7. WebMCP 101

   Join the WebMCP origin trial ↗

   Chrome's origin trial is time-limited early access for testing the proposed API, not proof of a stable cross-browser baseline.

About this page

This is a Mudpie reference profile, not an account, endorsement or claim that Alexandra Klepper contributed to Mudpie. The profile identifies an author, editor, maintainer, speaker or source publication connected to the linked work; it is not necessarily the article byline. Summaries are Mudpie's; the linked work remains the source of truth.