Extensions Marketplace

The Extensions Marketplace lets you browse, install, and manage MCP (Model Context Protocol) servers from the official registry directly through the Zubo dashboard or API. Instead of manually configuring MCP server commands and arguments, you can discover servers from the community, install them with one click, and have their tools automatically registered in Zubo.

Copy-Paste Task Cards

Secure API Access

Enable API auth and create a key before exposing ports beyond localhost.

zubo config set auth.enabled true
zubo auth create-key my-app

Set Local Model Fallback

Keep responses available during provider outages or API quota issues.

zubo config set failover '["openai","ollama"]'
zubo config set providers.ollama.model llama3.3

Common Errors

401 Unauthorized / Missing Bearer token

If auth.enabled is true, all /api/* calls require Authorization: Bearer <key>. Create a new key if needed.

curl -H "Authorization: Bearer YOUR_KEY" http://localhost:3000/api/dashboard/status

Provider Timeout / Upstream unavailable

Use failover and switch temporarily to a responsive provider or smaller model. Check logs for repeated timeout patterns.

zubo model openai/gpt-4o-mini
zubo logs --follow

Missing local model (Ollama/LM Studio)

If local providers fail, ensure the runtime is running and a model is installed.

ollama serve
ollama pull llama3.3

Browsing the Registry

The marketplace connects to the official MCP server registry and presents available servers with their metadata, descriptions, and tool counts. You can browse the full catalog or search for specific functionality.

Via the Dashboard

Open the web dashboard and navigate to the Extensions panel in the sidebar.
Click the Marketplace tab to view the available servers from the registry.
Use the search bar to filter servers by name or keyword (e.g., "filesystem", "database", "github").
Each server card shows the name, description, author, tool count, and install status.

Via the API

GET /api/mcp/marketplace?q=filesystem&category=utilities

Query parameters:

Parameter	Default	Description
`q`	—	Search query to filter servers by name or description.
`category`	—	Filter by category (e.g., `utilities`, `databases`, `apis`, `development`).
`limit`	50	Maximum results to return.
`offset`	0	Pagination offset.

Response:

{
  "servers": [
    {
      "name": "@modelcontextprotocol/server-filesystem",
      "description": "MCP server providing file system operations",
      "author": "Anthropic",
      "category": "utilities",
      "toolCount": 11,
      "installed": false,
      "version": "0.6.2",
      "homepage": "https://github.com/modelcontextprotocol/servers"
    }
  ],
  "total": 1
}

Installing MCP Servers

Installing an MCP server from the marketplace adds it to your Zubo configuration, downloads the required package, starts the server process, and automatically registers all of its tools. The entire process takes a few seconds.

Via the Dashboard

Find the server you want in the Marketplace tab.
Click the Install button on the server card.
If the server requires environment variables (API keys, paths, etc.), a configuration dialog appears. Fill in the required values and click Install.
The server connects automatically and its tools appear in the Installed tab with a green status indicator.

Via the API

POST /api/mcp/marketplace/:name/install
Content-Type: application/json

{
  "env": {
    "GITHUB_TOKEN": "ghp_abc123..."
  }
}

Install an MCP server by its registry name. The env field is optional and provides environment variables required by the server. The server is started immediately after installation.

Response:

{
  "success": true,
  "name": "@modelcontextprotocol/server-github",
  "tools": [
    "github__create_issue",
    "github__list_repos",
    "github__search_code",
    "github__create_pull_request"
  ],
  "toolCount": 4,
  "status": "connected"
}

Via the CLI

# Install from the marketplace
zubo mcp install @modelcontextprotocol/server-filesystem

# Install with environment variables
zubo mcp install @modelcontextprotocol/server-github \
  --env GITHUB_TOKEN=ghp_abc123...

# List installed MCP servers
zubo mcp list

Managing Installed Servers

Once installed, MCP servers are managed through the same interface as manually configured servers. You can view their status, restart them, or uninstall them.

Dashboard Management

Installed tab — shows all installed MCP servers with their name, status (connected/disconnected), tool count, and uptime. Marketplace-installed servers are marked with a marketplace icon.
Server details — click a server to view its tools, configuration, environment variables (masked), and connection log.
Restart — restart a server's connection. Useful after updating environment variables or when a server becomes unresponsive.
Uninstall — remove the server, stop its process, and deregister its tools from Zubo.

Uninstalling via the API

POST /api/mcp/servers/:name/uninstall

Uninstall an MCP server. The server process is terminated, its tools are deregistered, and the configuration is removed. Returns 204 No Content on success.

How It Works

When you install a server from the marketplace, Zubo performs the following steps:

Fetch metadata — retrieves the server's registry entry, including the npm package name, required command, arguments, and environment variable requirements.
Download package — runs npx -y <package-name> to download and cache the package locally. No global installation is performed.
Add to config — adds the server to the mcp.servers array in ~/.zubo/config.json with the appropriate command, arguments, and environment variables.
Start process — spawns the MCP server as a subprocess and initiates the JSON-RPC initialization handshake.
Discover tools — queries the server for its available tools and registers them in Zubo with the server name as a prefix (e.g., filesystem__read_file).

Marketplace-installed servers behave identically to manually configured ones. The only difference is the installation method — once installed, they appear in both the MCP configuration and the installed servers list.

API Endpoints

All marketplace endpoints are under /api/mcp and require authentication when auth.enabled is true.

Browse Marketplace

GET /api/mcp/marketplace?q=search&category=utilities

Search and browse the MCP server registry. See the Browsing the Registry section above for full query parameter and response documentation.

Get Server Details

GET /api/mcp/marketplace/:name

Get detailed information about a specific server in the registry, including its full description, required environment variables, available tools, and installation instructions.

Response:

{
  "name": "@modelcontextprotocol/server-filesystem",
  "description": "MCP server providing file system operations including reading, writing, and searching files.",
  "author": "Anthropic",
  "version": "0.6.2",
  "category": "utilities",
  "tools": [
    { "name": "read_file", "description": "Read the contents of a file" },
    { "name": "write_file", "description": "Write content to a file" },
    { "name": "list_directory", "description": "List directory contents" }
  ],
  "requiredEnv": [],
  "optionalEnv": ["ALLOWED_DIRECTORIES"],
  "installed": false,
  "homepage": "https://github.com/modelcontextprotocol/servers"
}

Install Server

POST /api/mcp/marketplace/:name/install
Content-Type: application/json

{
  "env": { "API_KEY": "..." }
}

Install an MCP server from the marketplace. See the Installing MCP Servers section above for full documentation.

Uninstall Server

POST /api/mcp/servers/:name/uninstall

Uninstall an MCP server. Works for both marketplace-installed and manually configured servers. The server process is stopped, tools are deregistered, and the configuration is removed.

Previous← Visual Workflows NextChannel Setup →