build-mcpb

Package local MCP servers with runtimes and dependencies into portable .mcpb archives.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill build-mcpb-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-mcpb
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/marketplaces/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcpb
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill build-mcpb-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires esbuild, and includes references (resource) components.

What problem does it solve?

This skill solves the challenge of distributing local MCP servers that require specific runtimes or local system access, allowing users to run complex tools without needing to manage Node.js or Python environments themselves.

Core Features & Use Cases

  • Runtime Bundling: Packages your MCP server code with its necessary runtime and dependencies into a single, portable .mcpb archive.
  • Local System Integration: Enables servers to securely interact with the local filesystem, desktop applications, and OS-level APIs.
  • Use Case: You have built a custom file-management tool that requires specific Node modules; use this skill to bundle it into a single file that a user can simply drag onto their Claude Desktop to install.

Quick Start

Use the build-mcpb skill to pack the current directory into a distributable .mcpb archive after validating the manifest.

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 for distribution to other users?

Package a local MCP server by bundling its code, runtime, and dependencies into a portable .mcpb archive. This allows users to run complex stdio-based tools without managing Node.js or Python environments themselves.

What is an .mcpb archive and when do I need it for local MCP servers?

An .mcpb archive is a portable bundle containing a local MCP server, its required runtime, and dependencies. You need it to distribute stdio-based servers that require direct access to local filesystems, OS APIs, or desktop applications.

How do I bundle MCP server dependencies and runtimes into a single file?

Bundle MCP server dependencies and runtimes into a single file using manifest-based configuration and esbuild. The process validates the manifest and packages the current directory into a distributable .mcpb archive.

Can I distribute stdio-based MCP servers that require local filesystem and OS API access?

Yes, you can distribute stdio-based MCP servers requiring local filesystem and OS API access. The .mcpb archive implements security validation to ensure bundled servers operate correctly within the host environment.

Does build-mcpb work with Node.js modules for desktop application integration?

Yes, build-mcpb works with Node.js modules for desktop application integration. It packages your MCP server code with necessary Node modules and runtime into a single file users can drag onto Claude Desktop to install.

What are the limitations of packaging local MCP servers into .mcpb archives?

Limitations of packaging local MCP servers into .mcpb archives include dependency on esbuild for bundling and restriction to stdio-based servers. The manifest-based configuration and security validation must pass before packing the current directory.