Publishing MCP Servers

BuilderStudio does not currently offer self-serve marketplace custom-node publishing. The live reusable extension surface today is published user MCP servers exposed from canvases.

What creators can do today

• Expose a published user MCP server from BuilderStudio.
• Choose whether that published endpoint is public or bearer-protected.
• Share direct-client setup with external MCP users.
• Let BuilderStudio operators add the published server to workspace registries for agent-node use.

Current publishing model

1. 1

   Build the MCP surface you want to expose

   The current marketplace story is about published MCP endpoints, not custom visual node bundles.

2. 2

   Choose the endpoint auth mode

   Public endpoints require no bearer token. Protected endpoints use separate owner-managed published-server credentials. Protected published endpoints use a separate owner-managed published-server bearer path, typically a umcp_ key when the server owner issues API keys. Workspacebuilder_ keys do not unlock direct external client access to those published endpoints.

3. 3

   Manage access for operators

   If you own the server, manage its published API keys from the canvas MCP Server panel's API Keys tab. If you do not own it, ask the server owner for the published-server bearer token or exact outbound Authorization header value that endpoint expects. BuilderStudio does not issue self-serve marketplace tokens for protected published servers yet.

4. 4

   Document both usage paths

   Share direct external-client setup for Cursor, Claude Code, or Codex, and separate workspace-registry install guidance for BuilderStudio agent-node use.

What is deferred

• Custom visual-node packaging and submission.
• Marketplace review and approval queues.
• Creator payouts or revenue share.
• Self-serve credential issuance for other operators using protected published servers.