build-mcpb

Package local MCP servers into distributable MCPB bundles with manifest validation.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Wizarck/eligia-skills --skill build-mcpb-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-mcpb
Source: https://github.com/Wizarck/eligia-skills/tree/main/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcpb
Command: npx skills add https://github.com/Wizarck/eligia-skills --skill build-mcpb-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn a local MCP server into a single installable MCPB package so users can run it without separately installing Node, Python, or your toolchain.

Core Features & Use Cases

  • Packages local MCP servers with manifest.json, bundled server code, and icons.
  • Covers Node and Python build flows, including dependency vendoring, validation, packing, signing, and install testing.
  • Emphasizes safe local-server design for filesystem, desktop app, and localhost integrations, with explicit security guardrails for paths, process spawning, and secrets.
  • Ideal when you need to distribute an offline-capable MCP server that runs on the user's machine rather than a remote endpoint.

Quick Start

Ask for help packaging your local MCP server into an MCPB bundle and validating the manifest, bundled dependencies, and installable output.

Frequently Asked Questions about build-mcpb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package a local MCP server into a single distributable file?

Package a local MCP server into a distributable MCPB bundle by validating the manifest.json, vendoring Node or Python dependencies, and configuring explicit launch settings to create one installable file.

What is MCPB bundling used for in desktop automation and filesystem integrations?

MCPB bundling packages local MCP servers requiring filesystem access or desktop automation into an offline-capable, installable file so users can run them without separately installing Node, Python, or your toolchain.

Can I bundle both Node and Python MCP servers into an MCPB package?

Yes, MCPB packaging covers both Node and Python build flows, including dependency vendoring, validation, packing, signing, and install testing for local MCP servers running on the user's machine.

What security guardrails are needed when packaging local MCP servers?

Safe local-server packaging requires security guardrails for path handling, process spawning, and secrets management to prevent unauthorized filesystem access or unsafe process execution during desktop automation tasks.

Does my MCP server need a manifest.json file to create an MCPB bundle?

Yes, a valid manifest.json is required to package a local MCP server into an MCPB bundle, along with bundled server code, runtime dependencies, explicit launch configuration, and bundled icons.

What's the best way to distribute an offline-capable MCP server for localhost integration?

Distribute an offline-capable MCP server by packaging it into an MCPB bundle with vendored dependencies, allowing localhost integration without requiring users to install the original runtime toolchain.