marketplace

This MCP server provides AI agents with access to the Upbound Marketplace. It exposes a standard MCP interface (transportable via stdio or HTTP) that enables tools to list, search, and manage marketplace packages, repositories, and assets. The HTTP transport is available at http://localhost:8765/mcp and supports JSON-RPC 2.0 methods such as tools/list and tools/call for interacting with the marketplace tools. The server is designed to work with both v1 and v2 marketplace APIs and includes composition-focused tools to assist with Crossplane configurations and functions. To use it, run the Docker image (or build from source) and connect your agent or client to the HTTP endpoint or to the stdio transport as configured by your environment. The available tools include search_packages, get_package_metadata, get_package_assets, get_repositories, reload_auth, and get_package_version_resources, each with a defined set of parameters for querying marketplace data and assets.

Prerequisites:

• Docker installed and running
• UP CLI installed and authenticated (for private marketplace access)
• Git installed for cloning the repository (optional if using prebuilt image)

Option 1: Use prebuilt Docker image (recommended)

1. Pull and run the image as described in the README example:

   docker run --name mcp-marketplace --rm -i -d -p 8765:8765 -v /path/to/your/.up:/mcp/.up:ro xpkg.upbound.io/upbound/marketplace-mcp-server-http:v0.1.0

2. Ensure UP CLI is authenticated so the server can access private resources:

   up login

3. Configure the MCP client to connect to the HTTP endpoint, for example in your agent or Claude/Desktop configuration, point to http://localhost:8765/mcp or the appropriate host if running remotely.

Option 2: Build from source

1. Clone the repository and navigate to it:

   git clone https://github.com/upbound/marketplace-mcp-server.git cd marketplace-mcp-server

2. Build the HTTP server binary (or the stdio implementation as needed):

   go build ./cmd/mcp-server go build ./cmd/mcp-http

3. Run the HTTP server locally:

   ./mcp-http

   Or run with Docker using the provided image (as shown in Option 1).

Notes:

• If you require access to private marketplace resources, you must have the UP CLI configured (up login) and mount your up config into the container as shown to reuse your identity.
• The HTTP API runs statelessly and uses JSON-RPC 2.0 calls (e.g., tools/list and tools/call).

Tips and cautions:

• When using Docker, mount your UP CLI configuration directory (typically ~/.up) into the container to enable authentication against the marketplace.
• The marketplace HTTP image version in the example is v0.1.0; using newer images may require updates to the mcpServers configuration if paths or endpoints change.
• If you plan to run agents that expect stdio transport, you can connect via the stdio implementation or run the binary directly as shown in the README examples.
• The available tools include: search_packages, get_package_metadata, get_package_assets, get_repositories, reload_auth, and get_package_version_resources, each with their configured parameters. Use the HTTP API to discover and invoke these tools, or run the stdio transport for native MCP clients.
• For local development, ensure port 8765 is accessible and not blocked by firewalls, and if running behind a proxy, configure the agent accordingly.