convez.ai
MCP ServerIntegração & APIsIntermediário
Bigsy

Clojars MCP Server

Bigsy/Clojars-MCP-Server

Resolva dependências Clojure direto no Claude via MCP

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que fornece ferramentas para consultar dependências do Clojars, o repositório de artefatos da comunidade Clojure. Integra-se nativamente com Claude Desktop, Cline e outros clientes MCP para resolver dependências e verificar versões de bibliotecas Clojure em tempo real.

Instalação

$npx convez-ai Bigsy/Clojars-MCP-Server

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
6
Forks
6
Acompanhando
1
Saúde
42%
Último commit
há 1 ano
Versão
—
Issues abertas
2
Contribuidores
3

Casos de uso

  • Verificar versão mais recente de bibliotecas Clojure durante desenvolvimento
  • Consultar histórico de versões de dependências para escolher a melhor
  • Validar se uma versão específica de um artefato existe no Clojars
  • Integrar gestão de dependências Clojure em workflows com IA

Veredito

MCP server bem estruturado e prático para quem trabalha com Clojure. A integração com Claude é direta, mas o escopo é restrito à comunidade Clojure — útil se faz parte do seu stack, irrelevante caso contrário.

README

A tradução para o português deste README ainda está na fila.

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

  1. Clone this repository:
git clone https://github.com/yourusername/clojars-deps-server.git
cd clojars-deps-server
  1. Install dependencies:
npm install
  1. Build the server:
npm run build
  1. 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.

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
Ver o original no GitHub

Bom para

Relacionados