
JFrog Remote MCP Server
io.github.jfrogPublished by GitHub account jfrogv0.1.1Updated Oct 26, 2026
MCP Server for JFrog, providing tools for development and artifact management.
The publisher's own server: Registry Mcp
Overview
Remote MCP server that connects AI coding assistants to the JFrog platform for artifact, build, catalog and security queries.
- What you can do
- Create and view projects, repositories and other JFrog components
- Find packages and versions, locate stored artifacts, and search builds with AQL
- Look up catalog package information, versions, vulnerabilities and curation status
- Get Xray security summaries, policy violations, scan/indexing status, and trace resources affected by a CVE or package
- Access over 100 tools spanning Access, Artifactory, Security, Curation, Distribution, AI Catalog, Grid, Workers, OneModel, Event, Evidence and AppTrust
- When to use it
- Useful when an AI coding assistant should answer questions about your JFrog platform in natural language, such as checking whether a package is approved, reviewing reported vulnerabilities and license requirements, or tracking projects and artifacts.
- Requirements
- A JFrog Cloud (SaaS) or self-managed subscription; an admin must enable the MCP server on a JPD. Connect to your platform URL with the /mcp path and authorize through an OAuth browser flow. No API keys or local installation are needed for the hosted server.
Installation
In SourceWeft
- Open JFrog Remote MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.jfrog%2Fjfrog-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"jfrog-remote": {
"type": "http",
"url": "https://myplatform.jfrog.github.io/mcp"
}
}
}README
JFrog Remote MCP Server
The Model Context Protocol (MCP) connects AI systems with external tools, data, and services using a standardized, lightweight interface.
JFrog MCP Server empowers developers, bringing the advanced capabilities of the JFrog platform to the development environment. The JFrog MCP Server integrates with IDEs and AI coding assistants such as VS Code, Cursor, Claude, Kiro, and Codex to respond to natural-language AI queries with rich, actionable information from the JFrog platform.
Among the capabilities you can access with direct, friendly AI interactions:
- Resource Management: Create and view projects, repositories, and other JFrog components.
- Artifact & Build Discovery: Find packages and their versions, locate where artifacts are stored, and search builds using AQL.
- Catalog and Curation: Access package information, versions, and vulnerabilities, and check curation status.
- Security Monitoring: Get Xray security summaries and policy violations for artifacts, check an artifact's scan/indexing status, and trace every resource impacted by a specific CVE or package.
Use these resources and real-time information for various use cases. For example:
- Ensure that only approved packages are used by developers during coding.
- Query the JFrog Catalog about OSS package versions, changes in reported vulnerabilities, and license requirements.
- Track and manage JFrog Projects and artifacts.
And much more. See the full tool reference for everything the server exposes.
Note: The JFrog MCP Server is now generally available (GA) on JFrog Cloud (SaaS). The self-managed server is in Beta. Individual tools marked Beta in the tool reference are experimental and must be enabled for your environment.
Remote Server Implementation
The JFrog MCP Server is hosted on JFrog Cloud, and the tools it provides to the client are continuously updated — you automatically get new features and improvements as they are released, with no installation or upgrade required on the client side.
You connect to the JFrog MCP Server using OAuth for authentication. This eliminates the need to manage API keys.
Note: Because this is a remote server, the tool set evolves on the server. The
TOOLS.mdreference reflects the current tool surface.
Set up the JFrog MCP Server
The JFrog Remote MCP Server is generally available (GA) to JFrog users with a Cloud (SaaS) subscription.
Subscription information: Supported on the Cloud (SaaS) and Self-Managed platforms for all licenses.
Self-Managed (Beta): A self-managed JFrog MCP Server is also available. See MCP Server Installation for Helm and Docker Compose deployment.
- An Admin user must enable the JFrog MCP Server on a JPD in the subscription.
- You can then add the JFrog MCP Server to an MCP client.
- Save the configuration file.
- Restart or refresh your MCP client. An OAuth window opens in your browser.
- Follow the prompts to authorize your MCP client to access the JFrog MCP Server.
In the examples below, replace <JFROG_PLATFORM_URL> with your JFrog platform URL (for example, https://mycompany.jfrog.io).
Visual Studio Code
Cursor
For more MCP clients (Kiro, Claude, Codex, and others), see Add the JFrog MCP Server to an MCP client.
Tools
The server exposes over 100 tools across Access, Artifactory, Security, Curation, Distribution, AI Catalog, Grid, Workers, OneModel, Event, Evidence, and AppTrust.
See the full reference in TOOLS.md.
Documentation
Source: README.md at commit 4df9a99
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Remote-Mcp integrations

Registry Mcp
com.remote-mcpOfficial publisher
Remote MCP server that lets an assistant search the official MCP registry and look up details on individual MCP servers.

Starmux — All-in-One Self-Hosted Remote MCP Server & Gateway
Published by GitHub account cookyecat
Self-hosted daemon that exposes filesystem, terminal, process and Git tools to AI clients over Streamable HTTP, and multiplexes other local MCP servers.

Remote MCP Server
Published by GitHub account CaSO44444
A remote MCP server hosted at a bare IP address, with no documented tools, description, or authentication details.

Sdp Remote Mcp
com.opentext
Official OpenText server embedded in Software Delivery Platform products, giving AI clients read and write access to backlogs, work items and delivery data.

ChromaDB Remote MCP Server
Published by GitHub account meloncafe
Self-hosted remote ChromaDB vector database server over streamable HTTP, letting assistants manage collections and documents and run semantic search.