MCP governance expands with new lead maintainer and core team additions

The Model Context Protocol is adding leadership as its governance load grows. In a blog post dated April 8, 2026, the MCP team said Den Delimarsky has moved from Core Maintainer to Lead Maintainer, joining David Soria Parra in that role, while Clare Liguori has joined the project as a Core Maintainer.

MCP is the standard that lets AI assistants and agent frameworks connect to external tools and data sources through a common protocol. As adoption has grown, so has the amount of work around the spec itself, including design discussions, issue triage, and the review of proposals that shape how the protocol behaves across different clients and servers.

The maintainer update frames the change as a response to that growth. More community participation usually means more requests for clarification, more proposed changes, and more coordination across working groups. In practice, that puts pressure on the small group of people who keep a protocol consistent while still moving it forward.

Delimarsky’s move into a shared Lead Maintainer role gives MCP a clearer top-level leadership structure. Lead maintainers typically help steer the project, set priorities, and coordinate decision-making when a protocol has to balance speed, compatibility, and long-term stability. Having two people in that role can also spread the workload when discussions get broad or contentious.

Liguori’s addition matters for a different reason. The blog post points to her experience with agent runtimes and developer tooling, areas that sit close to how MCP is used in practice. That background is relevant as the protocol continues to define how agents talk to tools, how those tools expose capabilities, and how developers wire the pieces together.

The timing also lines up with broader activity around MCP’s governance. The project has been dealing with a growing volume of SEP, or Specification Enhancement Proposal, work, along with contributions from the community. SEPs are the formal proposals used to suggest changes to the protocol, so a rising number of them usually means more architectural choices, more review cycles, and more effort to keep decisions documented.

MCP’s working groups are part of that process. They give maintainers and contributors a place to focus on specific topics, such as protocol behavior, implementation concerns, or how agents should handle events and triggers. That structure is useful for a protocol that has to work across different products and automation stacks without becoming fragmented.

The blog post does not describe a major technical change to the protocol itself. Instead, it shows the project adjusting its stewardship so it can keep pace with the amount of design and coordination work now flowing through the MCP ecosystem, with Delimarsky and Soria Parra at the top of the maintainer group and Liguori added to the core team.