Clojars-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_clojars_latest_versionC | Get the latest version of a Clojars dependency (Maven artifact) |
| check_clojars_version_existsB | Check if a specific version of a Clojars dependency exists |
| get_clojars_historyC | Get version history of a Clojars dependency |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.