Enable MCP Server Integration

Enable the JFrog MCP Server integration on your JFrog Platform Deployment after installation.

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:

Prerequisite	Details
JFrog MCP Server installed and running	See MCP Server Helm Chart Installation or MCP Server Docker Compose Installation.
Platform Admin role	Your account must have the Platform Admin role on your JFrog Platform Deployment.
Platform URL and access token	Required to register the MCP server integration.

Enable MCP Integration

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

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.

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.

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

📘
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:

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

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.
`consent_type`	Agreement type accepted during registration. `BETA` indicates the JFrog Online Beta Agreement.

Frequently Asked Questions

Q: Can I use an internal service URL for PLATFORM_URL?

No. Use the browser-accessible public-facing JPD URL, for example https://acme.jfrog.io. Do not use an internal URL such as http://artifactory:8082. The platform_url value becomes the OAuth redirect URI and must be publicly reachable.

Q: What does a 400 error mean?

A 400 error means the platform_url field was omitted or is invalid. Verify that platform_url is set to your public-facing JPD URL in the request body.

Q: How do I confirm the integration was enabled successfully?

A successful request returns HTTP 200 with "status": "ACTIVATED" in the response body.

Prerequisites

Enable MCP Integration

Q: Can I use an internal service URL for PLATFORM_URL?

Q: What does a 400 error mean?

Q: How do I confirm the integration was enabled successfully?

Related Topics