Keeping MCP manifests synchronized shouldn’t require manual work 🎯
Just released MCPB CLI v0.2.0 to solve a workflow problem I kept hitting while building MCP infrastructure.
The issue: Server implementations evolve, tools get added or modified, but manifests stay static. Manual updates are tedious and easy to forget. Eventually your manifest describes tools that don’t match what the server actually exposes.
To install: dotnet tool install -g mcpb.Cli
What v0.2.0 adds:
mcpb validate –dirname
The validate command now: ✅ Checks manifest references (icons, screenshots, entrypoints all point to valid files) ✅ Spins up your server to inspect actual tool implementations ✅ Updates manifest.json to match the real schema ✅ Keeps your manifest synchronized with your code
Working on agent infrastructure at Windows scale made this clear: reliable agent discovery depends on accurate manifests. When you’re managing multiple MCP servers, manual synchronization doesn’t work.
The workflow improvement is straightforward - validation and updates happen together. Your manifest stays current with your implementation without extra manual steps.
What MCP tooling gaps are you running into? 👇