What can you do with this server?

The Clojars MCP Server provides tools for fetching and verifying dependency information from Clojars, the Clojure community's artifact repository. With this server, you can: * Retrieve the latest version of any Clojars dependency using the get_clojars_latest_version tool (provide the dependency name in the format group/artifact). * Verify if a specific version of a Clojars dependency exists using the check_clojars_version_exists tool (provide both the dependency name and version).

Which integrations are available for this server?

Enables fetching dependency information from Clojars, the Clojure community's artifact repository, allowing users to get the latest version of dependencies and check if specific versions exist

How do I use Clojars-MCP-Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Clojars-MCP-Server what's the latest version of metosin/reitit?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

Clojars-MCP-Server

by Bigsy

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Clojars MCP Server

npm version

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.

Installation

Installing via npx

The quickest way to use the Clojars MCP Server is to run it directly with npx:

npx clojars-deps-server

You can also install it globally:

npm install -g clojars-deps-server

Installing via Smithery

To install Clojars Dependency Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install clojars-deps-server --client claude

Manual Installation

Clone this repository:

git clone https://github.com/yourusername/clojars-deps-server.git
cd clojars-deps-server

Install dependencies:

npm install

Build the server:

npm run build

Add the server to your Claude configuration:

For VSCode Claude extension, add to cline_mcp_settings.json (typically located at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/ on macOS):

{
  "mcpServers": {
    "clojars-deps-server": {
      "command": "node",
      "args": ["/path/to/clojars-deps-server/build/index.js"]
    }
  }
}

For Claude desktop app, add to claude_desktop_config.json (typically located at ~/Library/Application Support/Claude/ on macOS):

{
  "mcpServers": {
    "clojars-deps-server": {
      "command": "node",
      "args": ["/path/to/clojars-deps-server/build/index.js"]
    }
  }
}

After 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.

Related MCP server: PatternStack

Features

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

How It Works

When 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.

The server exposes three tools:

get_clojars_latest_version

{
  "name": "get_clojars_latest_version",
  "description": "Get the latest version of a Clojars dependency (Maven artifact)",
  "inputSchema": {
    "type": "object",
    "properties": {
      "dependency": {
        "type": "string",
        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
      }
    },
    "required": ["dependency"]
  }
}

check_clojars_version_exists

{
  "name": "check_clojars_version_exists",
  "description": "Check if a specific version of a Clojars dependency exists",
  "inputSchema": {
    "type": "object",
    "properties": {
      "dependency": {
        "type": "string",
        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
      },
      "version": {
        "type": "string",
        "description": "Version to check (e.g. \"0.7.2\")"
      }
    },
    "required": ["dependency", "version"]
  }
}

get_clojars_history

{
  "name": "get_clojars_history",
  "description": "Get version history of a Clojars dependency",
  "inputSchema": {
    "type": "object",
    "properties": {
      "dependency": {
        "type": "string",
        "description": "Clojars dependency name in format \"group/artifact\" (e.g. \"metosin/reitit\")"
      },
      "limit": {
        "type": "number",
        "description": "Number of versions to return (default: 15, max: 100)",
        "minimum": 1,
        "maximum": 100
      }
    },
    "required": ["dependency"]
  }
}

The 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:

The tool names explicitly indicate their purpose
The descriptions specify they're for "Clojars dependency (Maven artifact)"
The example formats show typical Clojars dependency patterns

Available Tools

3 tools

check_clojars_version_existsB

Check if a specific version of a Clojars dependency exists

ParametersJSON Schema

Name	Required	Description	Default
`dependency`	Yes	Clojars dependency name in format "group/artifact" (e.g. "metosin/reitit")
`version`	Yes	Version to check (e.g. "0.7.2")

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Check' implies a read-only operation, it doesn't specify whether this is a safe lookup, what happens on failure (e.g., error handling), or any rate limits or authentication requirements. The description is too minimal for a mutation-free tool with no annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (simple lookup with two parameters) and 100% schema coverage, the description is minimally adequate. However, with no output schema and no annotations, it lacks details on return values (e.g., boolean, error messages) or behavioral context, leaving gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, fully documenting both parameters (dependency and version) with examples. The description adds no additional parameter semantics beyond what the schema already provides, so it meets the baseline of 3 without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Check') and resource ('specific version of a Clojars dependency'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its siblings (get_clojars_history and get_clojars_latest_version), which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings or alternatives. There's no mention of use cases, prerequisites, or exclusions, leaving the agent with no contextual direction for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_clojars_historyC

Get version history of a Clojars dependency

ParametersJSON Schema

Name	Required	Description	Default
`dependency`	Yes	Clojars dependency name in format "group/artifact" (e.g. "metosin/reitit")
`limit`	No	Number of versions to return (default: 15, max: 100)

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't mention important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what format the version history is returned in. The description is minimal and lacks operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence that states the core purpose without any unnecessary words. It's front-loaded with the essential information and wastes no space on redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no annotations and no output schema, the description is incomplete for a tool with 2 parameters. While concise, it doesn't provide enough context about what the tool returns, how errors are handled, or operational constraints. For a tool that presumably returns structured version history data, more context would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with both parameters well-documented in the input schema. The description doesn't add any parameter semantics beyond what's already in the schema - it doesn't explain the dependency format further or provide additional context about the limit parameter. This meets the baseline expectation when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('version history of a Clojars dependency'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_clojars_latest_version' (which returns only the latest version) or 'check_clojars_version_exists' (which checks existence of a specific version).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings. There's no mention of alternatives, prerequisites, or contextual factors that would help an agent choose between 'get_clojars_history', 'get_clojars_latest_version', or 'check_clojars_version_exists'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_clojars_latest_versionC

Get the latest version of a Clojars dependency (Maven artifact)

ParametersJSON Schema

Name	Required	Description	Default
`dependency`	Yes	Clojars dependency name in format "group/artifact" (e.g. "metosin/reitit")

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get') but does not describe traits like whether it's a read-only operation, requires authentication, has rate limits, or what the output format might be. This is a significant gap for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It is appropriately sized for a simple tool and front-loaded with the core purpose, making it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not address behavioral traits, output format, or usage context, which are essential for an agent to effectively invoke this tool. The high schema coverage is insufficient to compensate for these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, fully documenting the single parameter 'dependency' with format examples. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('latest version of a Clojars dependency'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'check_clojars_version_exists' or 'get_clojars_history', which likely serve related but distinct purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools or contexts where this tool is preferred, leaving the agent to infer usage based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Aug 18, 2025
- First observedcheck_clojars_version_exists
- First observedget_clojars_history
- First observedget_clojars_latest_version

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Deps Dev A
io.github.pipeworx-io
deps.dev — Google's package metadata + dependency graph API
Developer Tools Code Analysis
362
MCPFax Dev Package Intelligence A
com.mcpscores
Is this dependency current, licensed, deprecated, or already carrying a CVE?
Developer Tools Security
51
devstack-mcp A
io.github.IsaiahDupree
Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
Developer Tools Code Analysis
101
Package Intel MCP A
io.github.selflabbs
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Developer Tools Code Analysis
2

Related MCP Servers

Daipendencyofficial
Documentation Access Developer Tools Code Analysis
daipendency
A
license
B
quality
D
maintenance
Get the narrative and API documentation for the exact version of any of your dependencies. (Only Rust is supported at the moment.)
Updated 2 years ago (2025-02-09 15:06 UTC)
1
22
57
MIT
PatternStack
Developer Tools Code Analysis Security
patternstack-ai
A
license
B
quality
D
maintenance
Provides crowdsourced package intelligence and security alerts for AI coding assistants by analyzing project dependencies and framework co-occurrence. It enables automated project scans, package alternative discovery, and data-driven recommendations across multiple programming ecosystems.
Updated 7 months ago (2026-01-29 04:53 UTC)
10
22
MIT
@4da/mcp-server
Security Developer Tools Code Analysis
4DA-Systems
A
license
A
quality
A
maintenance
Dependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.
Updated 12 hours ago (2026-09-05 17:40 UTC)
9
517
2
Apache 2.0
maven-mcp
Developer Tools Code Analysis Search
IvanMikhailenka
A
license
B
quality
D
maintenance
Enables searching Maven Central artifacts, retrieving versions, and analyzing dependencies via natural language.
Updated a year ago (2025-10-14 16:35 UTC)
5
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bigsy/Clojars-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Clojars MCP Server

Installation

Installing via npx

Installing via Smithery

Manual Installation

Features

How It Works

get_clojars_latest_version

check_clojars_version_exists

get_clojars_history

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Daipendencyofficial

PatternStack

@4da/mcp-server

maven-mcp

Appeared in Searches

Latest Blog Posts

MCP directory API