MCP Server Installation - General Availability

This section covers installing and configuring JFrog MCP Server 1.0.x, the General Availability (GA) release for self-managed environments. For the MCP Server overview, prerequisites, and bundled PostgreSQL details that apply to every release, see MCP Server Installation.

What's Different in 1.0.x

Compared to the Beta releases (0.442.x / 0.606.x), 1.0.x changes the following:

No install-time beta agreement. The Helm chart no longer uses consentToJfrogOnlineBetaAgreement, and the Docker Compose config.sh script no longer prompts you to accept a beta agreement.
Optional Beta tools. A small set of tools is released in Beta status. Registering the integration sets beta_tools_approved to false unless you pass true, which hides Beta tools. A Platform Admin can turn Beta tools on or off later without re-provisioning. See MCP Beta Tools.
Single tools reference. All tools for this release are listed in MCP Server Tools (1.0.x), with Beta tools marked.

Install and Configure 1.0.x

Follow these pages in order: install, enable the integration, then connect a client.

MCP Server Helm Chart Installation

Deploy the MCP server as a standalone Helm chart on Kubernetes and connect it to your JFrog Platform Deployment.

MCP Server Docker Compose Installation

Deploy the MCP server using Docker Compose for non-Kubernetes environments.

PostgreSQL for MCP Server

Optional: configure an external PostgreSQL database instead of the bundled one.

Enable MCP Server Integration

MCP Clients

Connect VS Code, Claude, Cursor, and other MCP clients to your self-managed MCP server.

Add the JFrog MCP Server to an MCP Client

Configure Visual Studio Code, Cursor, Kiro, Claude, or Codex to connect to your self-managed JFrog MCP Server.

MCP Server Tools (1.0.x)

Complete reference of all tools the MCP server exposes to connected clients.

MCP Beta Tools

Tools released in Beta status in 1.0.x, and how to opt in or out.

Disable the JFrog MCP Server

Disable the MCP service entirely, revoke all sessions, or remove an individual user's MCP access.

Frequently Asked Questions

This section provides answers to frequently asked questions.

plusFAQs

Q: Do I need to accept a beta agreement to install 1.0.x?

No. 1.0.x does not require accepting a beta agreement at installation. Using the optional Beta tools is governed by the JFrog Online Beta Agreement - MCP Server Beta Tools.

Q: Are Beta tools available by default?

No. When you register the integration, beta_tools_approved defaults to false, which hides Beta tools. A Platform Admin can set it to true at registration or later. See Enable MCP Server Integration.

Q: Can I turn Beta tools off after enabling them?

Yes. Send a PATCH request to /mcp/admin/platform-integrations/current with "beta_tools_approved": false. You do not need to re-provision the integration. See MCP Beta Tools.