Skip to main content
Glama
Bigsy

Clojars-MCP-Server

by Bigsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Clojars-MCP-Server

No user-submitted related servers found.

    Related Servers

    • Maven Tools MCP Server

      arvindand
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides live Maven Central dependency inspection with stability filtering, version comparison, CVE checks, and POM-aware upgrade recommendations for MCP-capable clients.
      35
      MIT

    • mcp-maven-deps

      kirich1409
      A
      license
      A
      quality
      A
      maintenance
      maven-mcp gives AI agents (Claude Code, Cursor, Codex, Grok Build and any MCP client) live knowledge about JVM dependencies. It looks up the latest versions on Maven Central, finds outdated dependencies in Maven, Gradle and version catalog files, checks known vulnerabilities via OSV.dev, pulls changelogs and licenses, and builds dependency graphs with deps.dev. It's a single-file Python 3.9+ serve
      21
      36
      MIT

    • maven-artifacts-mcp

      skhatri
      A
      license
      B
      quality
      D
      maintenance
      Provides Maven artifact version resolution with caching, logging, and pre-release filtering for Maven Central.
      1
      24 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: checking version existence, retrieving version history, and getting the latest version. The descriptions make it unambiguous what each tool does, and an agent would have no difficulty selecting the right tool for each specific query about Clojars dependencies.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get' or 'check' verbs and descriptive nouns like 'clojars_version_exists', 'clojars_history', and 'clojars_latest_version'. The naming is uniform, predictable, and uses snake_case throughout, making it easy for agents to understand and work with.

    Tool Count3/5

    With only 3 tools, the server feels thin for a dependency management domain, as it lacks basic operations like searching for dependencies, listing available artifacts, or fetching dependency metadata beyond version info. While the tools are well-defined, the count is borderline low for the apparent scope of interacting with Clojars.

    Completeness2/5

    There are significant gaps in the tool surface for a Clojars server. Missing are essential operations such as searching for dependencies, retrieving artifact details (e.g., authors, licenses), or managing dependencies (e.g., adding/removing). The current tools only cover version-related queries, leaving agents unable to perform common dependency management tasks, which will likely cause failures in broader workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources