JFrog MCP
Related Servers
Alternatives to JFrog MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for searching and listing components in Nexus Repository Manager 3 (Docker, Maven, npm, PyPI, etc.) with tools for repositories, components, Docker tags, and latest version.-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for Akamai CDN that enables searching properties, browsing EdgeWorker code, querying DNS zones, inspecting network lists, and translating error codes via natural language.161MIT
- FlicenseAqualityCmaintenanceA read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.4-
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for AI clients to browse and search project files securely, with configurable permissions, virtual paths, and key-based access.-
- AlicenseNot gradedqualityDmaintenanceSecure multi-source MCP server for reading local, GitHub, GitLab, Bitbucket, and network source code with read-only-by-default access, enabling AI assistants to inspect repositories safely.1MIT
TDQS
Scored across 10 tools
Each tool targets a distinct operation: health check, capabilities, repository listing, path listing, item metadata, properties, stats, tree traversal, file search, and latest files. The only potential ambiguity is between get_item_info and get_item_properties, but the descriptions clarify that info is general metadata while properties are specific key-value pairs.
Most tools follow a consistent get_/list_/find_ verb-noun pattern (e.g., get_item_properties, list_repositories, find_files). Minor deviations exist: jfrog_ping and jfrog_capabilities are verb/noun alone, and jfrog_latest_files uses an adjective instead of a verb, but the overall style is coherent and predictable.
Ten tools is well within the ideal range for a focused MCP server. Each tool addresses a specific task within the artifact repository domain, and the count feels neither sparse nor overwhelming.
The toolset covers the read-only/query surface thoroughly: repository listing, path browsing, metadata, properties, statistics, tree traversal, file search, and recent files. It lacks write operations (create/update/delete), but the tools are clearly scoped to inspection and discovery, so the absence does not create dead ends for its apparent purpose.