MCP Server Installation - Beta
Install the JFrog MCP Server Beta releases (0.442.x and 0.606.x) on self-managed JFrog Platform Deployments.
This section covers installing and configuring the JFrog MCP Server Beta releases, 0.442.x and 0.606.x, on self-managed environments. For the MCP Server overview, prerequisites, and bundled PostgreSQL details that apply to every release, see MCP Server Installation. New installations should use MCP Server Installation - General Availability.
JFrog MCP Server Beta
These releases are in beta. Client integration details may change as the feature evolves. By using this service, you agree to the JFrog MCP Server Beta Agreement.
What's Specific to the Beta Releases
The Beta releases require you to accept the JFrog Online Beta Agreement at installation time:
- Helm: You must set
consentToJfrogOnlineBetaAgreement: true(a YAML boolean) in yourwingman-values.yaml. The chart fails at template time if the value is missing or set to a string. See MCP Server Helm Chart Installation. - Docker Compose: The
config.shscript displays the Beta Agreement and requires you to enterybefore installation continues. See MCP Server Docker Compose Installation. - Integration registration: The registration response returns
"consent_type": "BETA". See Enable MCP Server Integration. - Tools reference: Each Beta release has its own tool list: Version 0.442 and Version 0.606.
Install and Configure the Beta Releases
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
Register the MCP server with your JFrog Platform Deployment after installation.
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 (Version 0.442)
Tools exposed by JFrog MCP Server version 0.442.
MCP Server Tools (Version 0.606)
Tools exposed by JFrog MCP Server version 0.606.
Disable the JFrog MCP Server
Disable the MCP service entirely, revoke all sessions, or remove an individual user's MCP access.
JFrog Online Beta Agreement
The agreement that governs self-managed use of the Beta releases.
Related Topics
- MCP Server Installation
- JFrog MCP Server Beta Agreement
- MCP Server Installation - General Availability
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: Do I need to accept the Beta Agreement to install 0.442.x or 0.606.x?
Yes. For Helm, set consentToJfrogOnlineBetaAgreement: true as a YAML boolean. For Docker Compose, enter y at the Beta Agreement prompt in config.sh.
Q: Which tools reference applies to my installation?
Use the page that matches your installed server version: MCP Server Tools (Version 0.442) or MCP Server Tools (Version 0.606).
Q: Should I start a new installation on a Beta release?
No. New installations should use MCP Server Installation - General Availability, which does not require an install-time beta agreement.
Updated 26 days ago