# Miguel Piedrafita

Canonical: https://mudpie.ai/authors/miguel-piedrafita/
Updated: 2026-09-20

Miguel Piedrafita is a lead contributor to MCP-B, the browser runtime and compatibility project around WebMCP. Read his project's docs when you need the distinction between the draft browser API and a practical runtime today.

Source: https://github.com/m1guelpf

Contribution history comes from the public WebMCP-org repositories; portrait comes from the linked public GitHub profile. Checked September 19, 2026.

## Referenced in 101

- [Security and human in the loop](https://docs.mcp-b.ai/explanation/design/security-and-human-in-the-loop) — Tool availability is not authorization. Sensitive actions still need application checks, clear previews and deliberate user confirmation.
- [Tool lifecycle and context replacement](https://docs.mcp-b.ai/explanation/architecture/tool-lifecycle-and-context-replacement) — Page tools change as navigation and app state change, so the runtime must replace stale context instead of accumulating an ever-growing tool list.
- [Spec status and limitations](https://docs.mcp-b.ai/explanation/design/spec-status-and-limitations) — WebMCP is still a draft and implementations differ; ship compatibility deliberately and avoid presenting one runtime as universal browser support.
- [What is WebMCP?](https://docs.mcp-b.ai/explanation/what-is-webmcp) — MCP-B explains WebMCP as the browser-facing contract and positions its own packages as compatibility and runtime infrastructure around that contract.
- [Choose your WebMCP runtime](https://docs.mcp-b.ai/how-to/choose-runtime) — Choose native, polyfill, extension or relay based on the agent host and browser you must support; no one path is the default everywhere.

This is a Mudpie reference profile, not an account or endorsement. The profile records an authority connected to the source; it is not necessarily the article byline.