Enable MCP Server Integration

After installing the JFrog MCP Server, enable the integration on your JFrog Platform Deployment (JPD) to make MCP tools available to connected clients.

Prerequisites

Before you begin, verify the following:

Enable MCP Integration

Enable the MCP integration using a direct API call to the Wingman service.

1. Generate an Admin Access Token
   In the JFrog Platform UI, go to Administration > User Management > Access Tokens and generate a token with admin privileges. Copy the token value.

2. Register the Platform Integration
   Run the following command, replacing <PLATFORM_URL> with the browser-accessible URL you use to open the JFrog UI (for example, https://acme.jfrog.io) and <ADMIN_TOKEN> with the token from Step 1. Do not use an internal service URL such as http://artifactory:8082.

   Bash

   curl -i -X POST "<PLATFORM_URL>/mcp/admin/platform-integrations/provision" \
     -H "Authorization: Bearer <ADMIN_TOKEN>" \
     -H "Content-Type: application/json" \
     -d '{"platform_url": "<PLATFORM_URL>"}'

   Optionally, add "beta_tools_approved": true to the JSON body to opt in to Beta tools at registration. If you omit the field, it defaults to false and Beta tools stay off. Setting beta_tools_approved to true means you accept the JFrog Online Beta Agreement - MCP Server Beta Tools. For the list of Beta tools, see MCP Beta Tools.

   Bash

   curl -i -X POST "<PLATFORM_URL>/mcp/admin/platform-integrations/provision" \
     -H "Authorization: Bearer <ADMIN_TOKEN>" \
     -H "Content-Type: application/json" \
     -d '{"platform_url": "<PLATFORM_URL>", "beta_tools_approved": true}'

   📘

   Why platform_url Is Required

   The platform_url value becomes the OAuth redirect URI (RFC 6749 §10.6) used during client authentication. There is no fallback to headers or environment variables. The field must be explicitly set to your public-facing JPD URL. Omitting it returns a 400 error.

   A successful request returns HTTP 200. The following is a sample response:

   JSON

   {
     "id": "465165c5-f5e6-4c05-a267-447b72b935bd",
     "client_id": "app@01krjhzfyztfdq0xs2wv7t0600",
     "status": "ACTIVATED",
     "remote_mcp_url": "https://acme.jfrog.io/mcp",
     "beta_tools_approved": false
   }

   Field	Description
   id	Unique identifier for this integration registration.
   client_id	OAuth application client ID assigned to this MCP integration.
   status	Activation state. ACTIVATED confirms the integration is registered and ready to use.
   remote_mcp_url	MCP endpoint URL registered with the platform. This is the URL users need when configuring their MCP client. See Add the JFrog MCP Server to an MCP Client.
   beta_tools_approved	Optional. Whether this integration has opted in to Beta tools. Defaults to false if omitted. Can be changed later without re-provisioning; see below.

3. Toggle Beta Tools After Registration
   To turn Beta tools on or off for an existing integration, run the following command. Set beta_tools_approved to true to enable Beta tools, or false to turn them back off.

   Bash

   curl -i -X PATCH "<PLATFORM_URL>/mcp/admin/platform-integrations/current" \
     -H "Authorization: Bearer <ADMIN_TOKEN>" \
     -H "Content-Type: application/json" \
     -d '{"beta_tools_approved": true}'

   This command updates the existing ACTIVATED integration in place. It does not create a new OAuth client, and you do not need to re-provision. The change takes effect the next time a connected client lists or calls tools. Setting beta_tools_approved to true means you accept the JFrog Online Beta Agreement - MCP Server Beta Tools. For the list of Beta tools, see MCP Beta Tools.

Frequently Asked Questions

This section provides answers to frequently asked questions.

Related Topics

• MCP Server Helm Chart Installation
• MCP Server Docker Compose Installation
• MCP Clients
• Add the JFrog MCP Server to an MCP Client
• MCP Beta Tools
• JFrog Online Beta Agreement - MCP Server Beta Tools