build-mcpb

Package MCP servers into standalone .mcpb archives with dependencies and configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It enables developers to package and distribute MCP servers as single, installable files that run independently on user machines.

Core Features & Use Cases

  • Create self-contained bundles including manifest, server code, and icon for local MCP servers.
  • Package the server with dependencies and configuration into a portable .mcpb archive.
  • Use case: A developer wants to distribute a desktop application powered by a local MCP server without requiring users to install Node or Python tools.

Quick Start

Use the build-mcpb skill to package your MCP server code and dependencies into a distributable bundle for deployment.

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 local desktop distribution?

You package an MCP server for local desktop distribution by bundling the server code, dependencies, manifest, and icon into a standalone .mcpb archive. This creates a portable file suitable for installation and execution without requiring users to install Node or Python tools.

What is an .mcpb file and when do I need it for server deployment?

An .mcpb file is a portable archive containing a self-contained MCP server bundle. You need it for server deployment when distributing desktop applications powered by local MCP servers, allowing users to run the application without installing Node or Python tools.

Can I distribute a local MCP server to users without requiring Node or Python?

Yes, you can distribute a local MCP server without requiring Node or Python by packaging the server with its bundled dependencies and configuration into a standalone .mcpb archive. This allows the desktop application to run independently on user machines.

What is included in a standalone MCP server bundle?

A standalone MCP server bundle includes the server code, bundled dependencies, configuration, manifest, and an icon. These components are packaged together into a portable .mcpb archive to ensure seamless user deployment and local execution on desktop machines.

What's the best way to create a portable archive for MCP server distribution?

The best way to create a portable archive for MCP server distribution is to use a packaging workflow that assembles the manifest, server code, and icon into a self-contained .mcpb file. This ensures all bundled dependencies and configurations are included and validated for seamless deployment.