MCP Server Installation
Deploy the JFrog MCP Server on self-managed environments to connect AI Agents to the JFrog Platform.
Deploy the JFrog MCP Server on self-managed environments to connect AI agents and coding assistants to your JFrog Platform. New installations should use the General Availability (1.0.x) release.
Subscription Information
This feature is supported on the Self-Managed platform with all licenses.
Wingman Service
The
wingmanservice serves the JFrog MCP Server.
The Model Context Protocol (MCP) connects AI systems with external tools, data, and services using a standardized, lightweight interface. MCP simplifies AI integration, reduces engineering overhead, and supports scalable, cross-platform automation.
The JFrog MCP Server is a remote MCP server that integrates with MCP clients hosted by IDEs and AI coding assistants such as Copilot or Cursor. The JFrog MCP Server provides structured configuration and usage information that is used to respond to AI queries. This improves and enriches responses to queries related to JFrog.
Choose a Release
The JFrog MCP Server has two self-managed release lines. The following table compares them:
| Area | General Availability (1.0.x) | Beta (0.442.x / 0.606.x) |
|---|---|---|
| Install-time agreement | Not required | JFrog Online Beta Agreement required |
| Helm consent value | Not used | consentToJfrogOnlineBetaAgreement: true required |
| Docker Compose beta prompt | None | config.sh prompts you to accept the Beta Agreement |
| Beta tools | Opt in with beta_tools_approved (defaults to false) | No separate opt-in |
| Tools reference | MCP Server Tools (1.0.x) | 0.442, 0.606 |
Installation Workflow
Both release lines follow the same sequence. Each release's section has the detailed procedures.
- Check the prerequisites listed on this page.
- Install the MCP Server using the Helm chart (Kubernetes) or Docker Compose (non-Kubernetes hosts).
- Enable the MCP Server integration on your JFrog Platform Deployment (JPD) with a Platform Admin access token.
- Connect an MCP client, such as Visual Studio Code, Cursor, or Claude, to
<JFROG_PLATFORM_URL>/mcp.
Prerequisites to Install the MCP Server
The JFrog MCP Server must be deployed in the same environment as your JFrog Platform Deployment (JPD). Before proceeding, see System Requirements for supported platforms and minimum requirements.
The following table lists the prerequisites for installing the JFrog MCP Server:
| Prerequisite | Requirement | Applies To |
|---|---|---|
| CPU | 2 | All methods |
| RAM | 6 GB | All methods |
| Storage | 50-100 GB | All methods |
| Architecture (x86-64) | Supported | All methods |
| Architecture (ARM64) | Supported | All methods |
| JFrog Platform Deployment (JPD) | A running JPD is required | All methods |
| PostgreSQL | 17.x (bundled by default) | All methods |
| Kubernetes | 1.27+ | Helm Chart methods only |
| Helm | 3.17+ | Helm Chart methods only |
| Docker Engine | 20.10 or later | Docker Compose only |
| Docker Compose | Required | Docker Compose only |
PostgreSQL Database
The JFrog MCP Server bundles PostgreSQL 17.x by default for both Helm and Docker Compose. No database setup is required.
- For Helm: To use an external database, set
postgresql.enabled: falsein your values file and provide connection details. - For Docker Compose: The configuration script asks whether to install the bundled PostgreSQL database or connect to an existing external database.
To configure an external database, see PostgreSQL for MCP Server for your release: General Availability or Beta. For HA, load balancing, and replication options, see the PostgreSQL documentation.
Related Topics
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: Which JFrog subscriptions support the MCP Server?
The JFrog MCP Server is supported on the Self-Managed platform with all licenses.
Q: Do I need to install the MCP Server separately from the JFrog Platform?
Yes. The MCP Server runs as a separate wingman service and must be deployed alongside your JFrog Platform Deployment using Helm or Docker Compose.
Q: What installation methods are supported?
Helm Chart and Docker Compose. Helm is recommended for Kubernetes environments. Docker Compose is available for non-Kubernetes hosts.
Q: Does the MCP Server need to be in the same environment as the JFrog Platform?
Yes. The JFrog MCP Server must be deployed in the same environment as your JFrog Platform Deployment (JPD).
Q: Which release should I install?
New installations should use the General Availability (1.0.x) release. Use the Beta guide only if you are already running, or specifically need, the 0.442.x or 0.606.x Beta release.
Updated about 2 months ago
