MCP Server Helm Chart Installation
Install the JFrog MCP Server as a standalone Helm chart on Kubernetes and connect it to your JFrog Platform Deployment.
Install the JFrog MCP Server on a self-managed environment using the Wingman Helm chart.
Prerequisites
Before you begin, verify the following:
| Prerequisite | Details |
|---|---|
| JFrog Platform Deployment (JPD) | A running JPD with a reachable URL and join key. |
| PostgreSQL | Bundled PostgreSQL 17.x by default. No setup required. To use an external database instead, see PostgreSQL for MCP Server. |
| Helm | 3.17+ or later. |
| Kubernetes | 1.27+ or later. |
Steps to Install the Wingman Chart
-
Add the JFrog Helm Charts repository to your Helm client.
helm repo add jfrog https://charts.jfrog.io -
Update the repository.
helm repo update -
Before installing the Wingman Helm chart, add the values for
joinKey,masterKey, andjfrogUrlin thewingman-values.yamlfile. You must also setconsentToJfrogOnlineBetaAgreementto the YAML booleantrue. The chart fails at template time if this value is absent or set to a string.## This is the wingman-values.yaml file global: jfrogUrl: <YOUR_PREVIOUSLY_RETRIEVED_BASE_URL> joinKey: <YOUR_PREVIOUSLY_RETRIEVED_JOIN_KEY> masterKey: <YOUR_MASTER_KEY> consentToJfrogOnlineBetaAgreement: trueSet these values in the
wingman-values.yamlfile: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.
-
Install the Wingman chart with the release name
wingman.helm upgrade --install wingman --namespace wingman --create-namespace jfrog/wingman-ai-app -f wingman-values.yaml -
Check the deployment status of your Wingman Helm chart.
helm status wingman --namespace wingman -
Find the name of the running pod.
kubectl --namespace wingman get pods -
Get the container logs.
kubectl --namespace wingman logs -f <name of the pod>
Frequently Asked Questions
Q: Where do I find the joinKey and masterKey?
Go to Administration > Security > General > Connection Details in your JFrog Platform Deployment.
Q: What happens if I omit consentToJfrogOnlineBetaAgreement?
The Helm chart fails at template time. Set the value to the YAML boolean true in your wingman-values.yaml.
Q: Can I use the bundled PostgreSQL database in production?
The bundled PostgreSQL is suitable for evaluation. For production, use an external PostgreSQL instance with HA or replication. See PostgreSQL for MCP Server.
Related Topics
- MCP Server Installation
- PostgreSQL for MCP Server
- MCP Server Docker Compose Installation
- Enable MCP Server Integration
JFrog MCP Server Beta
The JFrog MCP Server is in beta. Client integration details may change as the feature evolves. By using this service, you agree to the JFrog MCP Server Beta Agreement.
Updated 4 days ago
