# David Soria Parra

Canonical: https://mudpie.ai/authors/david-soria-parra/
Updated: 2026-09-20

David Soria Parra co-invented the Model Context Protocol and serves in its governance. His writing is the shortest route to the protocol's design intent, evolution and operating model.

Source: https://github.com/dsp

MCP governance identifies David as a co-inventor and lead maintainer; portrait comes from the linked public GitHub profile. Checked September 19, 2026.

## Referenced in 101

- [MCP architecture](https://modelcontextprotocol.io/specification/2026-07-28/architecture) — A host owns user experience and security boundaries, clients maintain one server connection each, and servers expose focused context and capabilities.
- [MCP transports](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports) — Local stdio and remote Streamable HTTP solve different connection problems while carrying the same protocol messages.
- [Build an MCP server](https://modelcontextprotocol.io/docs/2026-07-28/develop/build-server) — Start with one useful capability and a supported SDK, then prove the server through an inspector or real host before adding breadth.
- [MCP authorization](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization) — Remote MCP authorization builds on OAuth while keeping resource servers, authorization servers, clients and protected resources explicit.
- [MCP authorization security considerations](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/security-considerations) — Token passthrough, confused deputies, open redirects and excessive scopes turn a convenient connector into an account-compromise path.
- [MCP's first anniversary](https://blog.modelcontextprotocol.io/posts/2025-11-25-first-mcp-anniversary/) — MCP's first year moved the protocol from an Anthropic launch to broad infrastructure with a community process and a much larger compatibility burden.
- [Introducing the MCP Registry](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/) — A shared registry standardizes discovery metadata; it does not certify server quality, safety, uptime or real tool execution.
- [The MCP roadmap](https://blog.modelcontextprotocol.io/posts/2026-mcp-roadmap/) — The roadmap identifies the protocol's active pressure points so builders can avoid treating current gaps as permanent architecture.

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.