Upbound Marketplace MCP Server

A Model Context Protocol (MCP) server that provides AI agents with access to the Upbound Marketplace API. This server enables agents to search, discover, and manage marketplace packages and repositories, with a focus on helping users leverage marketplace resources for Crossplane compositions and package management.

Built using the mcp-go framework for robust MCP protocol compliance and performance.

Features

• Package Search: Search for packages across the Upbound Marketplace with advanced filtering
• Package Metadata: Get detailed information about packages including CRDs, examples, and documentation
• Asset Access: Retrieve package assets like CRDs, examples, docs, and package files
• Repository Management: Browse and manage repositories
• Authentication: UP CLI-based authentication for accessing private resources
• Multi-API Support: Supports both v1 and v2 marketplace APIs
• Composition Focus: Specialized tools for working with Crossplane compositions and functions

Installation

Quick start (recommended): run once as a long-lived HTTP server

This is the supported pattern for all MCP clients that can talk to an HTTP endpoint (Cursor, Claude Code, Cline, Continue, Zed, etc.). The server runs detached in a single container; any MCP client connects to it over HTTP. No container is started or stopped per MCP session, so there is nothing that can leave a broken container behind.

1. Log in with the UP CLI so the server has a session to reuse:

   up login
   

2. Start the server once, detached. Replace the .up path with your actual UP CLI config directory (see UP CLI config location below).

   docker run --name mcp-marketplace --rm -d -p 8765:8765 \
     -v "$HOME/.up:/mcp/.up:ro" \
     xpkg.upbound.io/upbound/marketplace-mcp-server-http:v0.1.0
   

   Verify it is serving:

   curl -s -X POST http://localhost:8765/mcp \
     -H 'Content-Type: application/json' \
     -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
   

3. Point your MCP client at it:

   {
     "mcpServers": {
       "marketplace": {
         "httpUrl": "http://localhost:8765/mcp"
       }
     }
   }
   

UP CLI config location

• macOS / Linux: ~/.up (e.g. /Users/you/.up or /home/you/.up)
• Windows: %USERPROFILE%\.up

Upgrading to a new image version

docker pull xpkg.upbound.io/upbound/marketplace-mcp-server-http:<new-tag>
docker rm -f mcp-marketplace
docker run --name mcp-marketplace --rm -d -p 8765:8765 \
  -v "$HOME/.up:/mcp/.up:ro" \
  xpkg.upbound.io/upbound/marketplace-mcp-server-http:<new-tag>

Alternative: stdio transport (for clients without HTTP support)

Some MCP clients (including older Claude Desktop builds) only support stdio transport and launch the server as a subprocess per session. In that case use the stdio image — but do not pass --name. A fixed container name can only ever be held by one container at a time, so if a previous session's container is still alive (client crash, lost stdio, --rm not firing) every new session will fail with Conflict. The container name "/mcp-marketplace" is already in use. Let Docker generate a unique name per session instead:

{
  "mcpServers": {
    "marketplace": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-v", "/Users/your-username/.up:/mcp/.up:ro",
        "xpkg.upbou

... [View full README on GitHub](https://github.com/upbound/marketplace-mcp-server#readme)