Skip to main content
Glama
Artifact Registry MCP Server

Artifact Registry MCP Server

by Pawangunjkar

Related Servers

Alternatives to Artifact Registry MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query Maven artifacts in JFrog Artifactory by reusing credentials from ~/.m2/settings.xml and providing tools like getting latest stable versions, listing artifacts, and checking dependency updates.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables autonomous AI agents and CI/CD runners to discover repository modules, scan outdated dependencies, fetch version histories, and apply verified dependency updates with major-version safety guardrails across polyglot monorepos.
      11 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connects AI coding assistants to the JFrog platform, enabling natural-language queries for resource management, artifact discovery, security monitoring, and catalog curation.
      15
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Jenkins through secure, contextual tools for querying and managing jobs, builds, nodes, queues, views, plugins, artifacts, and Groovy scripts, with configurable authentication and read-only safety.
      -

    TDQS

    A4.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct registry actions and resources, with confirmation-gated mutations separated from read-only operations. The main overlap is between artifact_save_credentials and artifact_connect, since connect also caches credentials, but descriptions clarify the difference.

    Naming Consistency4/5

    All tools use a consistent artifact_ prefix with snake_case naming, mostly following an artifact_verb_noun pattern. artifact_status is the minor exception, acting as a noun-only name rather than artifact_get_status.

    Tool Count5/5

    The 12-tool set is well-scoped for an artifact registry server, covering session management, discovery, verification, upload, promotion, and cleanup. Each tool appears to earn its place without excessive surface area.

    Completeness4/5

    The surface covers the core artifact supply-chain lifecycle well: connect, inspect, search, verify, upload, promote, and clean up. Minor gaps include no direct artifact download tool and no general-purpose artifact deletion beyond snapshot cleanup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues