Claude Desktop — One-Click Install (Bundle)

Why use a bundle

A bundle is the fastest way to add a Vectoralix MCP server to Claude Desktop. Anthropic's .mcpb format is a small zip that Claude Desktop knows how to install: pick auth, confirm, done. The manual path described on the next page edits claude_desktop_config.json by hand and is kept as a fallback for users who prefer to control their config file directly.

Download a bundle

1. Sign in to the Vectoralix dashboard and open MCP Servers.
2. Find the server you want to install. Each row has a download-arrow action labelled Create Bundle, next to Edit and Delete.
3. For a public server, clicking the action downloads the bundle immediately. For a private server, a modal opens first so you can choose how Claude Desktop should authenticate. The downloaded file is named vectoralix-<slug>.mcpb.

What's inside the .mcpb

A .mcpb is a zip containing a manifest.json that tells Claude Desktop how to launch the server, plus an icon and a small stub file. The manifest points Claude Desktop at npx -y mcp-remote <endpoint> — Anthropic's official local proxy that bridges Claude Desktop's stdio transport to your remote Vectoralix HTTP endpoint. The manifest also carries the server's name, description, author, icon, and a snapshot of its tools so Claude Desktop can render an accurate install preview.

Choosing an auth mode (private servers)

Public servers always download a public-shaped bundle and never show this prompt. Private servers ask you to pick one of two auth modes before the bundle is built.

Mode	When to pick it	What Claude Desktop does at install
OAuth (default)	You want users to sign in with their Vectoralix account in a browser.	The bundle has no token baked in. On first tool call Claude Desktop receives a 401 from the server and opens the browser sign-in flow.
Bearer token	You want to hand the user a long-lived token issued for this server.	Claude Desktop prompts for the token at install time as a required field, then injects it as an Authorization header on every request.

The Bearer option is disabled when the server has no live tokens: "No active tokens yet. Issue one in the Auth tab before picking this option." Issue a bearer token from the server's Auth tab first, then re-open the Create Bundle modal.

Install the bundle in Claude Desktop

1. Double-click the downloaded .mcpb file. Claude Desktop opens an install screen showing the server's name, description, author, icon, and the list of tools snapshotted at download time.
2. If the bundle was built in Bearer mode, paste the token into the required field. If it was built in OAuth mode, leave the auth section as-is — sign-in happens later in a browser.
3. Confirm. Claude Desktop adds the server to its config and restarts the connection automatically.
4. Open the tools tray in the composer. The server should appear with the count of tools loaded. For OAuth servers, the first tool call opens the browser sign-in window.

Verify

• In Claude Desktop, send a prompt that exercises one of the server's tools — for a File Search server, ask "Search my docs for X" and confirm results are returned.
• If something fails, test the same server in the Vectoralix Playground first. If it works there, the issue is local to Claude Desktop's install or token; if it fails there too, the problem is in the server configuration.

When to download a fresh bundle

The tools list embedded in the bundle is a snapshot taken at download time. After you add or remove tools and publish a new version, an already-installed server keeps working — Claude Desktop discovers tools at runtime from the remote endpoint. Only the install preview shown to anyone re-installing goes stale until you download and share a fresh .mcpb.