# Bigsy/Clojars-MCP-Server [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/Bigsy/Clojars-MCP-Server  
**GitHub Stars:** 6  
**npm Downloads (last month):** 74  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bigsy-clojars-mcp-server

## Description
Clojars MCP Server for upto date dependency information of Clojure libraries

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "clojars-mcp-server": {
    "command": "npx",
    "args": ["-y","The"]
  }
}
```

## Documentation

## What Bigsy/Clojars-MCP-Server MCP server does

Bigsy/Clojars-MCP-Server MCP server gives MCP clients access to version information for Clojure libraries published on Clojars, the Clojure community's artifact repository. Its scope is focused on dependency metadata rather than general package management or library documentation.

The server supports three dependency-related queries:

- Return the latest available version for a Clojars dependency.
- Test whether a particular dependency version exists.
- Return a dependency's version history, optionally constrained by a result limit.

Dependency identifiers must use the Clojars group/artifact form. The README uses `metosin/reitit` as an example.

## How it works

After an MCP client starts the server, the server advertises its tools to the client. The assistant can then select an appropriate tool when a request concerns a Clojars dependency. The tools are designed around version lookup, so their names and descriptions identify the repository and operation directly.

`get_clojars_latest_version` accepts one required `dependency` string and retrieves the current version. `check_clojars_version_exists` requires both `dependency` and `version`, allowing an agent to validate a version before using it. `get_clojars_history` requires `dependency` and accepts an optional numeric `limit`. The history limit defaults to 15 and may be set from 1 through 100.

## Setup and configuration

The published npm package is `clojars-deps-server`. The README documents direct execution with npx, global npm installation, Smithery installation, and a manual build from source. For direct local execution, use:

```bash
npx -y clojars-deps-server
```

A manual source setup consists of cloning the repository, running `npm install`, and building with `npm run build`. The resulting server can be registered in an MCP client configuration with Node and the generated `build/index.js` entry point.

The README provides configuration examples for Claude Desktop and the Cline VS Code extension. In both cases, the client launches the server as a local process and passes the built JavaScript file as an argument. No API key, token, or environment variable is documented as required.

## Tools and capabilities

The Bigsy/Clojars-MCP-Server MCP server exposes these tools:

- `get_clojars_latest_version`: looks up the newest version for a group/artifact identifier.
- `check_clojars_version_exists`: checks a named version for a group/artifact identifier.
- `get_clojars_history`: lists release versions, with a default history size of 15 and a maximum of 100.

These capabilities fit dependency review, upgrade checks, and agent-assisted Clojure project maintenance where the required information is version availability on Clojars.

## Limitations and notes

The documented interface is limited to Clojars dependency version information. The README does not describe tools for installing dependencies, inspecting transitive dependency graphs, retrieving artifact contents, or querying repositories other than Clojars. History requests also have a documented maximum of 100 returned versions.

The repository mentions compatibility with Cline, Roo Code, Cody, and Claude Desktop. Only Claude Desktop and Cline are covered by explicit configuration examples in the supplied material.

_Full upstream README: https://allmcps.com/mcp/bigsy-clojars-mcp-server/readme_