I’m excited to share that the MCPB (MCP Bundle) Working Group has been formalized under the governance of the modelcontextprotocol organization. This represents a significant step forward for the MCP ecosystem and the future of agentic workflows.
Why MCPB Matters
Over the past year of building MCP infrastructure at Windows scale, I’ve observed a consistent pattern: teams building MCP integrations are independently solving the same fundamental problems—packaging, distribution, security verification, and discoverability. Engineering cycles are being burned on reinventing solutions that should be standardized infrastructure.
The MCPB Working Group exists to change this dynamic.
What We’re Standardizing
The working group is focused on four core areas that repeatedly create friction for MCP developers:
Packaging Format
A standardized MCPB format means MCP servers can be packaged consistently regardless of the underlying implementation language or platform. Whether you’re building in .NET, Python, TypeScript, or any other language, the packaging story becomes uniform.
This isn’t just about convenience—it’s about enabling tooling. When the format is standardized, we can build sophisticated packaging tools, automated security scanners, and distribution pipelines that work for the entire ecosystem.
Security and Verification
Security verification has been a major friction point for enterprise MCP adoption. Teams need confidence that MCP servers are trustworthy before integrating them into production environments.
The working group is establishing built-in security and verification mechanisms as first-class concerns in the MCPB format. This means signature verification, provenance tracking, and security scanning become standard capabilities rather than custom solutions each team implements independently.
Registry Integration
Discoverability remains a challenge in the MCP ecosystem. Developers build excellent MCP servers, but connecting them with the agents and applications that need them requires manual configuration and documentation hunting.
Native registry integration in MCPB addresses this directly. MCP servers packaged in the standard format gain automatic discoverability through registry systems, making it trivial for agents to find and integrate capabilities they need.
Cross-Platform Distribution
MCP’s promise is cross-platform agent integration, but distribution mechanisms have been platform-specific and fragmented. MCPB provides cross-platform distribution that works consistently whether you’re deploying to Windows, macOS, Linux, or cloud environments.
The MCPB Project and Working Group
MCPB was initiated by Anthropic to address the fundamental packaging and distribution challenges facing the MCP ecosystem. Over the past few months, I’ve been collaborating closely with the Anthropic team—providing feedback on the MCPB specification, contributing spec changes, and porting the Node CLI to .NET with improved Windows support and cross-platform capabilities.
The working group is now formalized under the governance of the modelcontextprotocol organization on GitHub. The MCPB project itself is hosted at github.com/modelcontextprotocol/mcpb.
Anthropic recently published a detailed blog post about MCPB adoption that covers the technical details and broader community perspective on this standardization effort.
This collaboration brings together diverse perspectives from across the MCP ecosystem. At Microsoft, we’re building MCP integration at the operating system level—enabling Windows to support agentic workflows where MCP servers are first-class citizens. This gives us visibility into the infrastructure challenges teams face when deploying MCP at enterprise scale.
The broader MCP community, including the original Anthropic team and contributors from other organizations, brings expertise in agent-side integration patterns, developer experience, and cross-platform tooling.
Together, we’re ensuring MCPB addresses real-world needs from both the platform infrastructure and agent integration perspectives.
What This Means for Developers
If you’re building MCP servers today, the working group’s output will directly impact your workflow:
Faster Time to Production: Standardized packaging means less time on distribution plumbing, more time on agent capabilities. Teams that adopt standardized packaging patterns can ship agentic features significantly faster than teams managing custom packaging solutions.
Reduced Security Friction: Built-in verification mechanisms reduce the security review burden for both developers publishing MCP servers and enterprises consuming them.
Better Discoverability: Registry integration means your MCP servers become discoverable to agents without requiring manual configuration or documentation updates.
Ecosystem Interoperability: When the entire MCP ecosystem converges on standard packaging, cross-tool integration becomes seamless. An MCP server packaged for one agent environment works everywhere.
The Real Unlock
Building infrastructure for Windows to enable agentic workflows has taught me that standardization is what unlocks velocity at scale. When foundational infrastructure questions are answered definitively, engineering teams can focus on innovation rather than infrastructure.
The MCPB Working Group represents this principle applied to the MCP ecosystem. By standardizing packaging, distribution, security, and discovery, we’re removing the repetitive infrastructure work that every team currently handles independently.
When packaging becomes trivial, engineers focus on what makes their MCP servers valuable—the agent capabilities they expose—rather than the distribution plumbing required to deliver them.
What’s Next
The working group is actively defining the MCPB specification, with early implementations already in development. We’re working closely with the broader MCP community to ensure the specification addresses real needs and integrates with existing MCP tooling.
I’ll be sharing updates as the specification evolves and implementations become available. If you’re building MCP infrastructure, your feedback is valuable—the working group is designing for real-world use cases, and your perspective matters.
Join the Conversation
What MCP integration challenges are slowing your team down? Are there specific packaging, security, or distribution patterns you’ve found effective that should inform the standard?
I’m particularly interested in hearing from teams deploying MCP at scale. The challenges you’re solving independently are likely patterns the working group should address at the infrastructure level.
Connect with me on LinkedIn or reach out directly. This is foundational work for the MCP ecosystem, and getting it right requires input from the teams building on top of it.
The future of agentic workflows depends on solid infrastructure. The MCPB Working Group is building exactly that.