Clojars MCP Server

1# Clojars MCP Server
2 
3[![npm version](https://img.shields.io/npm/v/clojars-deps-server.svg)](https://www.npmjs.com/package/clojars-deps-server)
4 
5A [Model Context Protocol (MCP)](https://github.com/ModelContext/protocol) server that provides tools for fetching dependency information from [Clojars](https://clojars.org/), the Clojure community's artifact repository for Cline, Roo Code, Cody, Claude Desktop etc.
6 
7<a href="https://glama.ai/mcp/servers/i37857er6w"><img width="380" height="200" src="https://glama.ai/mcp/servers/i37857er6w/badge" alt="Clojars-MCP-Server MCP server" /></a>
8 
9## Installation
10 
11### Installing via npx
12 
13The quickest way to use the Clojars MCP Server is to run it directly with npx:
14 
15```bash
16npx clojars-deps-server
17```
18 
19You can also install it globally:
20 
21```bash
22npm install -g clojars-deps-server
23```
24 
25### Installing via Smithery
26 
27To install Clojars Dependency Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/clojars-deps-server):
28 
29```bash
30npx -y @smithery/cli install clojars-deps-server --client claude
31```
32 
33### Manual Installation
341. Clone this repository:
35```bash
36git clone https://github.com/yourusername/clojars-deps-server.git
37cd clojars-deps-server
38```
39 
402. Install dependencies:
41```bash
42npm install
43```
44 
453. Build the server:
46```bash
47npm run build
48```
49 
504. Add the server to your Claude configuration:
51 
52For VSCode Claude extension, add to `cline_mcp_settings.json` (typically located at `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/` on macOS):
53```json
54{
55  "mcpServers": {
56    "clojars-deps-server": {
57      "command": "node",
58      "args": ["/path/to/clojars-deps-server/build/index.js"]
59    }
60  }
61}
62```
63 
64For Claude desktop app, add to `claude_desktop_config.json` (typically located at `~/Library/Application Support/Claude/` on macOS):
65```json
66{
67  "mcpServers": {
68    "clojars-deps-server": {
69      "command": "node",
70      "args": ["/path/to/clojars-deps-server/build/index.js"]
71    }
72  }
73}
74```
75 
76After adding the server configuration, Claude will automatically detect and connect to the server on startup. The server's capabilities will be listed in Claude's system prompt under "Connected MCP Servers", making them available for use.
77 
78 
79## Features
80 
81- Get the latest version of any Clojars dependency
82- Check if a specific version of a dependency exists
83- Get version history of dependencies with configurable limits
84- Simple, focused responses
85- Easy integration with Claude through MCP
86 
87## How It Works
88 
89When this MCP server is configured in Claude's settings, it automatically becomes available in Claude's system prompt under the "Connected MCP Servers" section. This makes Claude aware of the server's capabilities and allows it to use the provided tools through the `use_mcp_tool` command.
90 
91The server exposes three tools:
92 
93### get_clojars_latest_version
94```json
95{
96  "name": "get_clojars_latest_version",
97  "description": "Get the latest version of a Clojars dependency (Maven artifact)",
98  "inputSchema": {
99    "type": "object",
100    "properties": {
101      "dependency": {
102        "type": "string",
103        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
104      }
105    },
106    "required": ["dependency"]
107  }
108}
109```
110 
111### check_clojars_version_exists
112```json
113{
114  "name": "check_clojars_version_exists",
115  "description": "Check if a specific version of a Clojars dependency exists",
116  "inputSchema": {
117    "type": "object",
118    "properties": {
119      "dependency": {
120        "type": "string",
121        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
122      },
123      "version": {
124        "type": "string",
125        "description": "Version to check (e.g. \"0.7.2\")"
126      }
127    },
128    "required": ["dependency", "version"]
129  }
130}
131```
132 
133### get_clojars_history
134```json
135{
136  "name": "get_clojars_history",
137  "description": "Get version history of a Clojars dependency",
138  "inputSchema": {
139    "type": "object",
140    "properties": {
141      "dependency": {
142        "type": "string",
143        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
144      },
145      "limit": {
146        "type": "number",
147        "description": "Number of versions to return (default: 15, max: 100)",
148        "minimum": 1,
149        "maximum": 100
150      }
151    },
152    "required": ["dependency"]
153  }
154}
155```
156 
157The 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 that these tools are appropriate for the task based on:
158- The tool names explicitly indicate their purpose
159- The descriptions specify they're for "Clojars dependency (Maven artifact)"
160- The example formats show typical Clojars dependency patterns
161 
162