build-mcpb

Package local MCP servers with bundled runtimes into installable .mcpb archives.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill build-mcpb-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-mcpb
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/build-mcpb
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill build-mcpb-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @anthropic-ai/mcpb, @modelcontextprotocol/sdk, esbuild, zod, and includes references (resource) components.

What problem does it solve? Distributing a local MCP server normally requires users to install Node or Python and resolve dependencies themselves. This Skill guides you through packaging an MCP server together with its runtime and dependencies into a single .mcpb file that installs on a machine with no toolchain present. ## Core Features & Use Cases - Manifest Authoring: Create a valid manifest.json defining the server entry point, mcp_config launch command, user_config install-time settings, and platform compatibility. - Build Pipelines: Bundle Node servers with esbuild or vendor Python dependencies into the archive, then validate and pack with the mcpb CLI. - Local Security Guidance: Implement path validation, spawn allowlists, and least-privilege patterns since MCPB provides no sandbox and runs with full user privileges. - Use Case: You built a filesystem MCP server that reads local documents. Use this Skill to bundle it with its Node runtime, define a directory picker in user_config, sign the .mcpb file, and distribute it to users who have no development environment. ## Quick Start Package my local MCP server into an installable .mcpb bundle with a manifest and bundled dependencies.

Frequently Asked Questions about build-mcpb

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

FAQPage Schema
How do I package an MCP server for distribution?▼

Bundle your server code and dependencies into a directory with a manifest.json, then run npx @anthropic-ai/mcpb pack to validate and zip it into a .mcpb file. Users install the single file without needing Node or Python installed.

What is an .mcpb file and what does it contain?▼

An .mcpb file is a zip archive containing a manifest.json with identity and launch configuration, a server directory with your MCP server code and bundled dependencies, and an optional icon. The host reads the manifest and launches the server as a stdio process.

When should I use MCPB instead of a remote MCP server?▼

Use MCPB when the server must run on the user's machine, such as reading local files, driving desktop apps, or calling localhost services. If your server only calls cloud APIs, a remote HTTP server avoids the packaging and local-security burden.

Does MCPB provide sandboxing or permission controls?▼

No, MCPB has no sandbox and no manifest-level permissions block. The server runs with full user privileges, so you must validate paths, prevent directory escapes, and allowlist spawned processes in your own tool handlers.

How do I add install-time user settings to an MCPB server?▼

Define a user_config section in manifest.json with typed fields such as directory pickers or sensitive values stored in the OS keychain. Reference them in mcp_config env using ${user_config.<key>} substitution.

Why does my MCPB server work on my machine but fail for users?▼

This almost always means a dependency was not actually bundled into the archive. Test the .mcpb on a machine without your dev toolchain, and vendor Python packages or bundle Node dependencies before packing.