MCP Server Helm Chart Installation

Install the JFrog MCP Server on a self-managed environment using the Wingman Helm chart.

Prerequisites

Before you begin, verify the following:

Steps to Install the Wingman Chart

1. Add the JFrog Helm Charts repository to your Helm client.

   Bash

   helm repo add jfrog https://charts.jfrog.io

2. Update the repository.

   Bash

   helm repo update

3. Before installing the Wingman Helm chart, add the values for joinKey, masterKey, and jfrogUrl in the wingman-values.yaml file.

   YAML

   ## This is the wingman-values.yaml file
   
   global:
     jfrogUrl: <YOUR_PREVIOUSLY_RETRIEVED_BASE_URL>
     joinKey: <YOUR_PREVIOUSLY_RETRIEVED_JOIN_KEY>
     masterKey: <YOUR_MASTER_KEY>

   Set these values in the wingman-values.yaml file:

   • jfrogUrl: The URL of your JFrog Platform Deployment (JPD).
   • joinKey: The secret key required to register and authenticate the MCP server with the JFrog Platform. You can retrieve this key from Administration > Security > General > Connection Details.
   • masterKey: The unique master key that the MCP server requires.

   If no database configuration is provided, the chart automatically deploys a bundled PostgreSQL 17.x instance alongside the MCP server. To use an external database instead, see PostgreSQL for MCP Server.

4. Install the Wingman chart with the release name wingman.

   Bash

   helm upgrade --install wingman --namespace wingman --create-namespace jfrog/wingman -f wingman-values.yaml

5. Check the deployment status of your Wingman Helm chart.

   Bash

   helm status wingman --namespace wingman

6. Find the name of the running pod.

   Bash

   kubectl --namespace wingman get pods

7. Get the container logs.

   Bash

   kubectl --namespace wingman logs -f <name of the pod>

Frequently Asked Questions

This section provides answers to frequently asked questions.

Related Topics

• MCP Server Installation
• PostgreSQL for MCP Server
• MCP Server Docker Compose Installation
• Enable MCP Server Integration
• MCP Beta Tools