Clojars

The Clojars MCP Server provides three tools that let Claude fetch and verify dependency information from the Clojars repository. get_clojars_latest_version returns the most recent version of a given Clojars artifact, check_clojars_version_exists confirms whether a specific version is available for a dependency, and get_clojars_history retrieves a configurable list of historical versions for a dependency. These tools are designed to be called through Claude’s MCP interface, enabling you to request dependency data in a structured JSON format. To use them, configure the MCP server in Claude so it appears under Connected MCP Servers, then invoke the tools by name with the appropriate input schema. The input schemas ensure you provide the dependency in the conventional "group/artifact" format (for example, "metosin/reitit").

Prerequisites:

• Node.js and npm installed on your system
• Access to the command line/terminal

Option 1: Run via npx (easyest for temporary use)

1. Ensure Node.js is installed.
2. Run the MCP server directly with npx: npx clojars-deps-server

Option 2: Install globally with npm (persistent, system-wide access)

1. Install the package globally: npm install -g clojars-deps-server
2. Run the server (if a start script is configured, you might run a specific command as per package.json): clojars-deps-server

Option 3: Install via Smithery (Claude integration)

1. Install Smithery CLI if you haven’t already: npx -y @smithery/cli install clojars-deps-server --client claude
2. Follow Smithery prompts to complete the installation and connect to Claude.

Option 4: Manual installation (from source)

1. Clone the repository: git clone https://github.com/yourusername/clojars-deps-server.git cd clojars-deps-server
2. Install dependencies: npm install
3. Build the server (if a build step exists): npm run build
4. Start the server or configure Claude to point to the built entry (e.g., build/index.js) as shown in the README example.

Notes and tips:

• The server exposes three MCP tools designed for dependency/version queries on Clojars: get_clojars_latest_version, check_clojars_version_exists, and get_clojars_history. Each tool uses a JSON-structured input schema to validate requests.
• The input for dependency names should follow the standard format "group/artifact" (e.g., "metosin/reitit").
• If you run via npx or npm, ensure your environment variables or network access permit fetching data from Clojars.
• In Claude's configuration, the server is typically referenced with command "node" and a path to the built entry point if you’re running from a local build. When using npx, Claude will resolve the package name at runtime.
• If you encounter rate limits or network issues fetching from clojars.org, consider caching results or implementing a retry strategy in your workflow.
• The MCP server’s capabilities will appear under Claude’s system prompt in the Connected MCP Servers section once configured.