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.

📘

Subscription Information

This feature is supported on the Self-Managed platform with all licenses.

📘

Wingman Service

The wingman service 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.

Install the JFrog MCP Server on self-managed environments and connect it to your MCP clients:

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.

Prerequisites for installing the JFrog MCP Server:

PrerequisiteRequirementApplies To
CPU2All methods
RAM6 GBAll methods
Storage50-100 GBAll methods
Architecture (x86-64)SupportedAll methods
Architecture (ARM64)SupportedAll methods
JFrog Platform Deployment (JPD)A running JPD is requiredAll methods
PostgreSQL17.x (bundled by default)All methods
Kubernetes1.27+Helm Chart methods only
Helm3.17+Helm Chart methods only
Docker Engine20.10 or laterDocker Compose only
Docker ComposeRequiredDocker 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 instead, set postgresql.enabled: false in your values file and provide connection details. To use an external database instead, see PostgreSQL for MCP Server.
  • For Docker Compose: The configuration script installs a bundled PostgreSQL database. During setup, you are prompted to use this bundled instance or connect to an existing external database. To use an external database instead, see PostgreSQL for MCP Server.

There are several ways to configure external PostgreSQL for redundancy, including HA, load balancing, and replication. For more information, see the PostgreSQL documentation.

Frequently Asked Questions
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).

🚧

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.