I’m happy to share two updates to the maintainer team: Clare Liguori is joining the Core Maintainer group, and Den Delimarsky is joining me as a Lead Maintainer.
When we introduced the MCP governance model last summer, the goal was to make sure the protocol could keep growing without any one person becoming a bottleneck. That has held up well through two specification releases, the move to the Agentic AI Foundation (AAIF), and a steady increase in SEP volume, and these changes give the project the leadership capacity it needs for what comes next.
Welcoming Clare Liguori as Core Maintainer
I’m pleased to welcome Clare Liguori to the Core Maintainer team.
Clare is a Senior Principal Engineer at Amazon Web Services, where she works on agentic AI developer tooling. Her current focus is Kiro and the Strands Agents SDK, and over more than a decade at AWS she has also worked on AWS Proton, Amazon ECS, the AWS Code Suite, and several open source projects.
Clare has been bringing that depth of developer-tooling and agent-runtime experience directly into MCP’s design work, particularly the discussions around unsolicited tasks, the agent execution model, and the Triggers & Events working group. She knows firsthand what the protocol has to look like inside production agent runtimes serving large numbers of developers. As those proposals move through the SEP process over the coming year, that perspective will keep the spec grounded in what client implementers actually need. I’m glad to have her at the table.
Welcome, Clare!
Den Delimarsky Joins as Lead Maintainer
Den Delimarsky is stepping up from Core Maintainer to Lead Maintainer, joining me in that role.
Den is a Member of Technical Staff at Anthropic, where he works across the MCP ecosystem: the specification, the SDKs, governance, and the developer experience around all of it. Before Anthropic he was a Principal Product Engineer in Microsoft’s CoreAI division, and he brings a wealth of experience across developer tools, SDKs, and security tooling.
Den’s work is most visible in authorization and security. He co-authored the authorization specification, brought RFC 8707 Resource Indicators into the spec, and has continued to build on it through SEP-835, SEP-1024, and the SEP-2350 family of proposals, among others. He also led the 2025-11-25 specification release, co-leads the Security Interest Group, and built a contribution tracker that gives SDK and spec maintainers a birds-eye view of activity across the project’s repositories.
I’m glad to have Den as a partner in this role, and I’m looking forward to what we can do together for the protocol in the years ahead.
What’s Next
MCP continues to grow at a pace none of us could have predicted, and that growth wouldn’t be possible without the people who keep it moving every day: the SDK maintainers, the working group facilitators, and everyone who has authored or reviewed a SEP. Thank you.
With this team in place, I’m excited to keep working alongside the maintainer group to evolve the protocol and make sure MCP keeps pace with what the community needs from it. If you’d like to get involved, the governance docs explain how the project is organized, the Contributor Ladder shows how people grow into these roles, the roadmap shows where we’re headed, and our Discord is the best place to talk to the people working on it. Come build with us.