Clojars MCP Server

Obtains latest dependency details for Clojure libraries.

Local serverstdio

What is the Clojars MCP server?

If you want an AI assistant working directly with Clojars, the clojars mcp server is the bridge. Obtains latest dependency details for Clojure libraries.

What Clojars does

A Model Context Protocol (MCP) server that provides tools for fetching dependency information from Clojars, the Clojure community's artifact repository for Cline, Roo Code, Cody, Claude Desktop etc.

Key capabilities

  • Get the latest version of any Clojars dependency
  • Check if a specific version of a dependency exists
  • Get version history of dependencies with configurable limits
  • Simple, focused responses
  • Easy integration with Claude through MCP

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

  • get_clojars_latest_version — The get_clojars_latest_version tool exposed by this server
  • check_clojars_version_exists — The check_clojars_version_exists tool exposed by this server
  • get_clojars_history — The tool names and descriptions are specifically designed to help Claude understand that these tools are for retrieving version information from Clojars. When

Installing the clojars mcp server

The server is distributed via npm as The, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Clojars sits in that group, and the shape of its toolset — get_clojars_latest_version, check_clojars_version_exists, get_clojars_history — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the clojars mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
get_clojars_latest_versionThe get_clojars_latest_version tool exposed by this server.
check_clojars_version_existsThe check_clojars_version_exists tool exposed by this server.
get_clojars_historyThe tool names and descriptions are specifically designed to help Claude understand that these tools are for retrieving version information from Clojars. When users ask about Clojars dependencies, Claude can recognize th

How to install the Clojars MCP server

{
  "mcpServers": {
    "clojars": {
      "command": "npx",
      "args": ["-y", "The"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Clojars to get clojars latest version.
  • Use Clojars to check clojars version exists.
  • Use Clojars to get clojars history.

Frequently asked questions

It connects Clojars to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (get_clojars_latest_version, check_clojars_version_exists, get_clojars_history) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Clojars directly.