build-mcpb

Package a local MCP server with its runtime into a portable .mcpb bundle.

12|2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/hasanraiyan/resume --skill build-mcpb-hasanraiyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-mcpb
Source: https://github.com/hasanraiyan/resume/tree/main/.agent/skills/build-mcpb
Command: npx skills add https://github.com/hasanraiyan/resume --skill build-mcpb-hasanraiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Build-mcpb helps you distribute a local Model Context Protocol (MCP) server in a way that runs on the user’s machine without requiring them to install Node.js or Python, while still enabling local filesystem access and OS-level integrations.

Core Features & Use Cases

  • Bundle a local MCP server with its runtime: Create a single .mcpb package that contains the server code plus bundled dependencies so hosts can launch it as a stdio MCP server.
  • Generate a valid MCPB manifest: Define identity, entry point, compatibility requirements, and install-time user configuration for parameters like a root directory.
  • Secure-by-design guidance for local security: Apply path containment checks, avoid command injection, add size limits, and treat tool inputs as untrusted because MCPB has no platform sandbox.

Quick Start

When you want to package a local filesystem MCP server, run the build steps to pack the bundle into a .mcpb file and test it with an interactive pack/validate flow before signing and distribution.

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 so users don't need Node or Python installed?

To package a local MCP server without requiring Node or Python, you bundle the server code and its runtime dependencies into a portable .mcpb archive. This bundle includes everything needed to launch the server as a stdio process on end-user machines.

What is an MCPB bundle and when do I need it for filesystem servers?

An MCPB bundle is a portable archive containing a local Model Context Protocol server and its runtime. You need it when distributing servers that interact with the local filesystem, desktop apps, localhost services, or OS-level APIs to end-users lacking preinstalled runtimes.

How do I generate a manifest.json for an MCP server package?

You generate a manifest.json for an MCP server package by defining the server identity, entry point via mcp_config, and compatibility requirements. The manifest also specifies install-time user_config parameters, such as defining a root directory for filesystem access.

Does MCPB packaging provide sandboxing for local filesystem access?

MCPB packaging does not provide platform sandboxing for local filesystem access. You must apply secure-by-design guidance, including path containment checks, avoiding command injection, adding size limits, and treating all tool inputs as untrusted.

Can I bundle an MCP server that integrates with desktop apps and OS-level APIs?

You can bundle an MCP server that integrates with desktop apps and OS-level APIs using the .mcpb format. This packaging approach explicitly supports local servers interacting with operating system features rather than cloud-only HTTP integrations.

What are the limitations of distributing local MCP servers via MCPB archives?

Limitations of distributing local MCP servers via MCPB archives include the lack of a platform sandbox and the necessity to treat tool inputs as untrusted. You must manually implement path containment, command injection prevention, and size limits for security.