Build Mcpb

anthropics/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcpb

作者 anthropicsb78ac49cdc6b无许可证47K 个星标收录于 2026年11月20日更新于 2026年11月20日仓库今天更新

This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP", discusses ".mcpb files", mentions bundling a Node or Python runtime with their MCP server, or needs an MCP server that interacts with the local filesystem, desktop apps, or OS and must be installable without the user having Node/Python set up.

精选仅含说明AI 与智能体软件开发
AI 生成的概览

指导将本地 MCP 服务器与其运行时打包为单个 .mcpb 文件,实现一键安装。

功能
说明如何构建 MCPB 包:一个包含 manifest.json、服务器代码、打包依赖和图标压缩包。涵盖清单字段(server 类型、mcp_config 的 command/args/env、user_config、compatibility)、Node 与 Python 的构建流程(esbuild 打包或依赖 vendoring),以及用 mcpb CLI 校验、打包和签名。同时强调清单层面没有沙箱,路径校验与进程白名单必须在工具处理逻辑中自行实现。
适用场景
适用于分发需要访问本地文件系统、桌面应用、localhost 服务或操作系统 API,且要求用户无需安装 Node 或 Python 即可使用的本地 MCP 服务器。不适用于仅调用云端 API 的服务器,那类应做成远程 HTTP 服务器。
运行要求
需要 Node.js 及 npm/npx、@anthropic-ai/mcpb CLI(init、validate、pack、sign),示例服务器还需 MCP SDK 与 zod;Python 项目需用 pip 将依赖放入子目录。测试使用 MCP inspector,安装通过 Claude Desktop 完成。仅为说明文档,不含脚本。

Build an MCPB (Bundled Local MCP Server)

MCPB is a local MCP server packaged with its runtime. The user installs one file; it runs without needing Node, Python, or any toolchain on their machine. It's the sanctioned way to distribute local MCP servers.

MCPB is the secondary distribution path. Anthropic recommends remote MCP servers for directory listing — see https://claude.com/docs/connectors/building/what-to-build.

Use MCPB when the server must run on the user's machine — reading local files, driving a desktop app, talking to localhost services, OS-level APIs. If your server only hits cloud APIs, you almost certainly want a remote HTTP server instead (see build-mcp-server). Don't pay the MCPB packaging tax for something that could be a URL.


What an MCPB bundle contains

my-server.mcpb              (zip archive)├── manifest.json           ← identity, entry point, config schema, compatibility├── server/                 ← your MCP server code│   ├── index.js│   └── node_modules/       ← bundled dependencies (or vendored)└── icon.png

The host reads manifest.json, launches server.mcp_config.command as a stdio MCP server, and pipes messages. From your code's perspective it's identical to a local stdio server — the only difference is packaging.


Manifest

json
{  "$schema": "https://raw.githubusercontent.com/anthropics/mcpb/main/schemas/mcpb-manifest-v0.4.schema.json",  "manifest_version": "0.4",  "name": "local-files",  "version": "0.1.0",  "description": "Read, search, and watch files on the local filesystem.",  "author": { "name": "Your Name" },  "server": {    "type": "node",    "entry_point": "server/index.js",    "mcp_config": {      "command": "node",      "args": ["${__dirname}/server/index.js"],      "env": {        "ROOT_DIR": "${user_config.rootDir}"      }    }  },  "user_config": {    "rootDir": {      "type": "directory",      "title": "Root directory",      "description": "Directory to expose. Defaults to ~/Documents.",      "default": "${HOME}/Documents",      "required": true    }  },  "compatibility": {    "claude_desktop": ">=1.0.0",    "platforms": ["darwin", "win32", "linux"]  }}

server.type — node, python, or binary. Informational; the actual launch comes from mcp_config.

server.mcp_config — the literal command/args/env to spawn. Use ${__dirname} for bundle-relative paths and ${user_config.<key>} to substitute install-time config. There's no auto-prefix — the env var names your server reads are exactly what you put in env.

user_config — install-time settings surfaced in the host's UI. type: "directory" renders a native folder picker. sensitive: true stores in OS keychain. See references/manifest-schema.md for all fields.


Server code: same as local stdio

The server itself is a standard stdio MCP server. Nothing MCPB-specific in the tool logic.

typescript
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";import { z } from "zod";import { readFile, readdir } from "node:fs/promises";import { join } from "node:path";import { homedir } from "node:os";
// ROOT_DIR comes from what you put in manifest's server.mcp_config.env — no auto-prefixconst ROOT = (process.env.ROOT_DIR ?? join(homedir(), "Documents"));
const server = new McpServer({ name: "local-files", version: "0.1.0" });
server.registerTool(  "list_files",  {    description: "List files in a directory under the configured root.",    inputSchema: { path: z.string().default(".") },    annotations: { readOnlyHint: true },  },  async ({ path }) => {    const entries = await readdir(join(ROOT, path), { withFileTypes: true });    const list = entries.map(e => ({ name: e.name, dir: e.isDirectory() }));    return { content: [{ type: "text", text: JSON.stringify(list, null, 2) }] };  },);
server.registerTool(  "read_file",  {    description: "Read a file's contents. Path is relative to the configured root.",    inputSchema: { path: z.string() },    annotations: { readOnlyHint: true },  },  async ({ path }) => {    const text = await readFile(join(ROOT, path), "utf8");    return { content: [{ type: "text", text }] };  },);
const transport = new StdioServerTransport();await server.connect(transport);

Sandboxing is entirely your job. There is no manifest-level sandbox — the process runs with full user privileges. Validate paths, refuse to escape ROOT, allowlist spawns. See references/local-security.md.

Before hardcoding ROOT from a config env var, check if the host supports roots/list — the spec-native way to get user-approved directories. See references/local-security.md for the pattern.


Build pipeline

Node

bash
npm installnpx esbuild src/index.ts --bundle --platform=node --outfile=server/index.js# or: copy node_modules wholesale if native deps resist bundlingnpx @anthropic-ai/mcpb pack

mcpb pack zips the directory and validates manifest.json against the schema.

Python

bash
pip install -t server/vendor -r requirements.txtnpx @anthropic-ai/mcpb pack

Vendor dependencies into a subdirectory and prepend it to sys.path in your entry script. Native extensions (numpy, etc.) must be built for each target platform — avoid native deps if you can.


MCPB has no sandbox — security is on you

Unlike mobile app stores, MCPB does NOT enforce permissions. The manifest has no permissions block — the server runs with full user privileges. references/local-security.md is mandatory reading, not optional. Every path must be validated, every spawn must be allowlisted, because nothing stops you at the platform level.

If you came here expecting filesystem/network scoping from the manifest: it doesn't exist. Build it yourself in tool handlers.

If your server's only job is hitting a cloud API, stop — that's a remote server wearing an MCPB costume. The user gains nothing from running it locally, and you're taking on local-security burden for no reason.


MCPB + UI widgets

MCPB servers can serve UI resources exactly like remote MCP apps — the widget mechanism is transport-agnostic. A local file picker that browses the actual disk, a dialog that controls a native app, etc.

Widget authoring is covered in the build-mcp-app skill; it works the same here. The only difference is where the server runs.


Testing

bash
# Interactive manifest creation (first time)npx @anthropic-ai/mcpb init
# Run the server directly over stdio, poke it with the inspectornpx @modelcontextprotocol/inspector node server/index.js
# Validate manifest against schema, then packnpx @anthropic-ai/mcpb validatenpx @anthropic-ai/mcpb pack
# Sign for distributionnpx @anthropic-ai/mcpb sign dist/local-files.mcpb
# Install: drag the .mcpb file onto Claude Desktop

Test on a machine without your dev toolchain before shipping. "Works on my machine" failures in MCPB almost always trace to a dependency that wasn't actually bundled.


Reference files

  • references/manifest-schema.md — full manifest.json field reference
  • references/local-security.md — path traversal, sandboxing, least privilege

来源与署名

来源:anthropics/claude-plugins-official位于plugins/mcp-server-dev/skills/build-mcpb提交b78ac49

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

在 README 中添加徽章

向读者展示该技能已收录于 SourceWeft,徽章链接到本页。

“Listed on SourceWeft”徽章预览
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-anthropics-claude-plugins-official-build-mcpb.svg)](https://sourceweft.com/skills/gh-anthropics-claude-plugins-official-build-mcpb?utm_source=readme&utm_medium=badge)

举报或申请下架