Sync open source content 🐝 (from c8fdab9ebf695cb52b14e635d0e16c63cc55789b)

Author: beezythebot

docs/standalone-mcp/build-server.mdx

@@ -149,7 +149,7 @@ The generated MCP server includes a comprehensive file structure with TypeScript
 
 ## Running your MCP server locally
 
-You can run your MCP server from the generated code, a published npm package, or the generated Desktop Extensions (DXT) package.
+You can run your MCP server from the generated code, a published npm package, or the generated MCP Bundle (MCPB) package.
 
 ### Local development setup
 
@@ -196,12 +196,12 @@ Once you've published your MCP server to npm (following our [SDK publishing guid
 
 **Note:** You must first publish your package to npm before you can test it using this configuration.
 
-### Using the generated DXT
+### Using the generated MCPB
 
-For the most user-friendly testing experience, use the generated DXT package. Claude Desktop and other MCP clients can load DXT files directly:
+For the most user-friendly testing experience, use the generated MCPB package. Claude Desktop and other MCP clients can load MCPB files directly:
 
-- **Locate your generated DXT file** in the output directory (it typically has a `.dxt` extension).
-- **Install the DXT** in your MCP client following the client's installation process.
+- **Locate your generated MCPB file** in the output directory (it typically has a `.mcpb` extension).
+- **Install the MCPB** in your MCP client following the client's installation process.
 - **Configure environment variables** if your server requires authentication.
 
 ## Advanced configuration
@@ -248,7 +248,7 @@ You can further limit the subset of tools mounted on an MCP server by specifying
 
 ## Distribution and hosting options
 
-Speakeasy generates MCP servers with three primary distribution methods. You can distribute your server as an npm package, a Cloudflare Worker, or a DXT file. These methods aren't mutually exclusive — most customers use all three approaches to serve different use cases.
+Speakeasy generates MCP servers with three primary distribution methods. You can distribute your server as an npm package, a Cloudflare Worker, or an MCPB file. These methods aren't mutually exclusive — most customers use all three approaches to serve different use cases.
 
 ### Distribute your MCP server on npm
 
@@ -286,28 +286,28 @@ Cloudflare hosting enables OAuth authentication flows and eliminates the need fo
 
 Follow the [Cloudflare deployment guide](/docs/standalone-mcp/cloudflare-deployment) for detailed instructions on using Cloudflare hosting.
 
-### Generate your MCP server as a DXT file
+### Generate your MCP server as an MCPB file
 
-In addition to a drag-and-drop experience for end users (particularly in Claude Desktop), DXT provides the following benefits:
+In addition to a drag-and-drop experience for end users (particularly in Claude Desktop), MCPB provides the following benefits:
 
 - **User-friendly installation:** Drag-and-drop installation in Claude Desktop.
 - **Guided setup:** Nicely prompts end-users for API keys and auth credentials.
 - **Self-contained format:** All dependencies and metadata bundled together.
 - **Cross-platform compatibility:** Works across different operating systems and MCP clients.
 
-Speakeasy automatically generates [Anthropic Desktop Extensions (`.dxt` files)](https://github.com/anthropics/dxt) as part of MCP server generation. The DXT includes:
+Speakeasy automatically generates [MCP Bundle (`.mcpb` files)](https://github.com/anthropics/dxt) as part of MCP server generation. The MCPB includes:
 
 - **A `manifest.json` file**, containing metadata describing your MCP server
 - **All the necessary server files**, packaged for distribution
 - **Tool descriptions and parameters**, automatically inferred from your OpenAPI document
 - **Icon and branding assets**, if provided
 
-You can customize the generated DXT manifest through the `gen.yaml` configuration file:
+You can customize the generated MCPB manifest through the `gen.yaml` configuration file:
 
 ```yaml
 targets:
   mcp-typescript:
-    dxtManifestOverlay:
+    mcpbManifestOverlay:
       icon: "https://example.com/my-icon.png"
       displayName: "My Custom API Tools"
       description: "Custom description for my MCP server"
@@ -328,8 +328,8 @@ When building MCP servers with Speakeasy:
 - **Test thoroughly:** Verify that your MCP server works with different clients.
 - **Version your APIs:** Use semantic versioning for your OpenAPI documents.
 - **Monitor performance:** Track the usage and performance of your MCP tools.
-- **Provide clear branding:** Include a `.png` icon file in your project for automatic [DXT](https://www.anthropic.com/engineering/desktop-extensions) icon detection.
-- **Customize DXT metadata:** Use `dxtManifestOverlay` in `gen.yaml` to provide custom display names and descriptions.
+- **Provide clear branding:** Include a `.png` icon file in your project for automatic [MCPB](https://www.anthropic.com/engineering/desktop-extensions) icon detection.
+- **Customize MCPB metadata:** Use `mcpbManifestOverlay` in `gen.yaml` to provide custom display names and descriptions.
 
 ## Next steps