Two ways MCP servers reach your AI: the open .mcpb packaging format (common on Claude Desktop), or a remote MCP URL (Cursor, Codex, ChatGPT, Claude Code, and most clients). On MCPBundles we connect hosted servers with the MCP URL — this page explains the format and when each path fits.
Looking for the technical .mcpb spec (manifest fields, ZIP layout, examples)? Read the MCPB file format reference →
Just like .dmg files on Mac or .exe files on Windows
.mcpb file is the installer for AI toolsThe .mcpb format is the open standard for packaging and installing MCP servers, maintained by the Model Context Protocol project. It's portable, simple, and works with a double-click.
Everything bundled together
Double-click to install
Can bridge to hosted backends
Some .mcpb packages ship a small local proxy instead of a full server. The proxy forwards tool calls to a hosted backend where credentials and updates are managed centrally.
When a publisher ships an `.mcpb` package for Claude Desktop
You'll need Claude Desktop installed on your computer. Download it from claude.ai/download
Obtain an .mcpb file from a trusted publisher — a vendor site, GitHub release, or your organization's extension directory.
Open the file in Claude Desktop. It reads the manifest, installs the server, and prompts for any credentials the package declares.
Open Claude Desktop and your MCP server's tools are ready. Ask Claude what tools it has access to.
On MCPBundles, use the MCP URL or one-click install links on each server page. The `.mcpb` format is how other publishers package servers for Claude Desktop.
Universal - works everywhere
Works with ChatGPT, Cursor, Windsurf, Claude Code, and any MCP client
Just copy the URL and paste into your AI's connector settings
MCP server changes take effect immediately, no reinstallation
https://mcp.mcpbundles.com/bundle/sales-pipelineClaude Desktop, Claude Code & MCP for Windows
Double-click to install, no manual configuration needed
Supported by Claude Desktop, Claude Code, and MCP for Windows
Single file a publisher can distribute to a team
sales-pipeline-bundle.mcpbA cloud-connected `.mcpb` package and an MCP URL can point at the same backend. On MCPBundles, open any server page, copy the MCP URL, or use the install link for your client.
Connect with the MCP URL and get enterprise-grade infrastructure behind every server
No local server setup or maintenance. Tools run on MCPBundles infrastructure.
Server improvements and new tools deploy automatically—no reinstallation needed.
Configure API keys once in your dashboard. They're encrypted and injected automatically.
One MCP server aggregates tools from 5+ different APIs with unified authentication.