Installing from Marketplace

Installing a marketplace MCP server means adding a published server to a workspace registry so that BuilderStudio agent nodes in that workspace can discover and call its tools. This is the BuilderStudio-internal consumption path. It is different from direct external-client setup, where Cursor, Claude Code, or Codex connect straight to the server's published endpoint.

Install vs direct client

A published MCP server supports two consumption paths. Choose the one that matches where you want to call the tools.

1Install (this page):2- adds the published server to a workspace registry3- makes the tools available to Agent nodes in that workspace4- protected installs can save outbound auth during install, or later on the Agent node5 6Direct external client:7- connects Cursor, Claude Code, or Codex straight to the published endpoint8- /api/user-mcp/<workspaceId>/<slug>9- public endpoint needs no bearer token; protected endpoint needs owner-managed auth

Install a server into a workspace

1. 1

   Open the server detail page

   Review the description, category, and whether the published endpoint is public or protected. Confirm the server is the one you want before installing.

2. 2

   Choose the target workspace

   Install registers the server in a specific workspace registry. Pick the workspace whose Agent nodes should be able to call the server's tools.

3. 3

   Handle protected-server auth

   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. For a bearer-protected server, save the owner-provided outbound auth during install if you already have it. Otherwise you can skip it during install and add it later. 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 or defer the Agent-node auth

   If you skipped auth during a protected install, complete it later from Agent node > MCP Servers > Auth headers before expecting runs to succeed. Public servers need no extra auth.

After install

• The published server is discoverable by Agent nodes in the workspace you installed it into.
• Outbound auth for protected servers is editable later on the Agent node, so you can rotate or add the owner-provided token without reinstalling.
• A workspace install does not grant direct external-client access; that path uses the server's published endpoint and its own auth.