Marketplace Overview

The live BuilderStudio marketplace currently centers on published MCP servers and a smaller set of curated templates. Marketplace MCP servers support two different consumption paths: direct external-client access through the published endpoint, and BuilderStudio-internal workspace registry installs for agent-node use.

What is live today

• Published MCP server detail pages with auth and client-setup guidance.
• Workspace registry installs so Agent nodes can discover published servers.
• Public published endpoints for direct Cursor, Claude Code, or Codex access when the server is public.
• Protected published endpoints with owner-managed published-server credentials when bearer auth is enabled.

Published MCP server paths

1Path 1: direct external MCP client -> /api/user-mcp/<workspaceId>/<slug>2Path 2: BuilderStudio marketplace install flow -> workspace registry entry (editable later from an Agent node)3 4Direct external client auth:5- public endpoint: no bearer token6- protected endpoint: separate owner-managed published-server bearer auth7 8BuilderStudio workspace install:9- adds the published server to a workspace registry10- protected installs can save outbound auth during install, or later on the Agent node if skipped

How to evaluate a server

1. 1

   Open the server detail page

   Review the description, category, direct-client endpoint, and whether the published endpoint is public or protected.

2. 2

   Decide how you want to use it

   Choose between direct external MCP setup for Cursor, Claude Code, or Codex, and a BuilderStudio workspace registry install for agent-node use.

3. 3

   Check the auth contract

   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. 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

   Finish the BuilderStudio-specific setup

   If you install a bearer-protected server into a workspace, save the owner-provided auth material during install if you already have it. Otherwise finish that Agent-node auth step later before expecting runs to succeed.

What is not live

• Self-serve marketplace token issuance for someone else's protected published server.
• Marketplace custom-node publishing for the current MVP.
• A generic “one click” install that makes protected published servers callable everywhere without operator setup.