JFrog Remote MCP Server

What JFrog Remote MCP Server does

JFrog Remote MCP Server MCP server exposes JFrog platform capabilities to MCP-compatible clients, including development environments and AI coding assistants. It is intended for teams that want an AI client to retrieve JFrog information and perform supported resource-management actions through natural-language requests.

The server covers resource management for projects, repositories, and other JFrog components. It also supports artifact and build discovery, including package version searches, artifact location lookups, and build searches using AQL. Catalog and curation tools provide package versions, vulnerability information, license requirements, and curation status.

Security-focused tools return JFrog Xray summaries and policy violations, report whether an artifact has been scanned or indexed, and help trace resources affected by a CVE or package. The repository states that the complete surface contains more than 100 tools across JFrog services such as Access, Artifactory, Security, Curation, Distribution, AI Catalog, Grid, Workers, OneModel, Event, Evidence, and AppTrust.

How it works

JFrog Remote MCP Server MCP server runs remotely on JFrog Cloud rather than as a client-side installation. An MCP client sends requests to the JFrog endpoint, and the server returns information or performs supported operations using the tools available on the service.

Authentication uses OAuth, so client configuration does not require manually managed API keys. Because the tools are hosted remotely, JFrog can update the available tool set without requiring a client-side installation or upgrade. The repository notes that the tool reference may change as the hosted service evolves.

The remote endpoint uses the JFrog platform URL followed by /mcp. The exact platform URL depends on the JFrog environment and subscription.

Setup and configuration

An administrator must first enable the JFrog MCP Server on a JPD in the subscription. After that, add the server to an MCP client using its remote URL, save the client configuration, and restart or refresh the client. The client opens an OAuth browser flow; follow the prompts to authorize access.

For Visual Studio Code, configure an MCP server entry with a URL such as https://<JFROG_PLATFORM_URL>/mcp. Cursor uses the same endpoint in its mcpServers configuration. Documentation also describes setup for Kiro, Claude, Codex, and other clients.

The remote service is generally available for JFrog Cloud users. A self-managed deployment is available in beta, with Helm and Docker Compose installation documented separately.

Tools and capabilities

Use JFrog Remote MCP Server MCP server to:

• Create and inspect projects, repositories, and related resources.
• Find packages, artifact versions, storage locations, and builds.
• Search builds with AQL.
• Query package catalog and curation information.
• Review vulnerabilities, licenses, and Xray policy violations.
• Check artifact scan or indexing status.
• Identify resources affected by a CVE or package.

Individual tools marked Beta in the tool reference are experimental and must be enabled for the relevant environment.

Limitations and notes

The server depends on a JFrog subscription and administrator enablement. The hosted tool set is not fixed: the repository’s TOOLS.md describes the current surface, while new features and changes may be released remotely. Self-managed availability is marked beta, and some individual tools are experimental. Client compatibility also depends on whether the chosen MCP client supports the remote endpoint and OAuth authorization flow.