MCP Jfrog MCP Server

Mcp jfrog mcp server connects MCP Jfrog to AI assistants that speak the Model Context Protocol. MCP server for using the JFrog Artifactory API.

What MCP Jfrog does

Model Context Protocol (MCP) Server for the JFrog Platform API, enabling repository management, build tracking, release lifecycle management, and more.

Key capabilities

• Repository Management — Create and manage local, remote, and virtual repositories
• Build Tracking — List and retrieve build information
• Runtime Monitoring — View runtime clusters and running container images
• Mission Control — View associated JFrog Platform instances
• Artifact Search — Execute powerful AQL queries to search for artifacts and builds
• Catalog and Curation — Access package information, versions, vulnerabilities, and check curation status
• Xray — Access scan artifacts summary, group by severity per artifact

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

• Returns — Platform readiness status
• Inputs — - key (string): Repository key
• Prerequisites — The Prerequisites tool exposed by this server

Installing the mcp jfrog mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 5 environment variables: JFROG_ACCESS_TOKEN, JFROG_URL, ACCESS_TOKEN, YOUR_JFROG_INSTANCE_URL, YOUR_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js v18 or higher - Docker (if using Docker deployment, See Docker Deployment ) - A valid JFrog platform instance with appropriate permissions - Access to create and manage access tokens in your JFrog platform instance

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Jfrog sits in that group, and the shape of its toolset — Returns, Inputs, Prerequisites — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by jfrog, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp jfrog mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.