Just shipped: Platform metadata support in MCPB schema 🚀

Working with the Anthropic team and MCP Contributors community, I’ve merged support for platform-specific metadata into the MCPB schema using the _meta property pattern.

Small change, bigger implications 🤖

Bridging the schemas: MCPB (desktop bundles) and server.json (registry) have largely evolved in parallel. Different contexts, different needs. This starts bringing them closer together by adopting the same extensibility pattern the official registry uses.

Why convergence matters: When desktop MCP servers and web-based implementations use aligned patterns, the ecosystem gets stronger. Tools that work with one schema can more easily work with the other. Knowledge transfers. The learning curve flattens.

Platform flexibility without fragmentation: Each platform can now define conventions for their environment (Windows-specific coming soon) while using shared extensibility mechanisms. macOS, web, mobile can all do the same through _meta.

The technical choice: We could have kept MCPB and server.json separate, optimizing each for its context. Instead, we’re investing in convergence where it makes sense.

Building at OS scale means thinking beyond your local constraints: → Every shared pattern creates ecosystem leverage → Every divergence creates friction

This is one step toward a more cohesive MCP ecosystem where desktop and web implementations speak the same language. ⚡

What other areas would benefit from schema alignment across the MCP ecosystem? 👇

Updated: