maven-central-mcp 0.2.2 → 0.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -11,7 +11,7 @@ import { checkMultipleDependenciesHandler } from "./tools/check-multiple-depende
11
11
  import { compareDependencyVersionsHandler } from "./tools/compare-dependency-versions.js";
12
12
  const server = new McpServer({
13
13
  name: "maven-central-mcp",
14
- version: "0.2.2",
14
+ version: "0.2.4",
15
15
  });
16
16
  let cachedRepos = null;
17
17
  function getRepositories() {
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "maven-central-mcp",
3
- "version": "0.2.2",
3
+ "version": "0.2.4",
4
4
  "description": "MCP server for Maven Central dependency intelligence",
5
5
  "main": "./dist/index.js",
6
6
  "type": "module",
7
7
  "bin": {
8
- "maven-central-mcp": "dist/index.js"
8
+ "maven-central-mcp": "./dist/index.js"
9
9
  },
10
10
  "scripts": {
11
11
  "build": "tsc",
@@ -19,7 +19,7 @@ Scan the current project for Maven/Gradle dependencies and report available upda
19
19
  - For Gradle files: find `implementation`, `api`, `compileOnly`, `testImplementation` etc. with group:artifact:version
20
20
  - For `pom.xml`: find `<dependency>` blocks with `<groupId>`, `<artifactId>`, `<version>`
21
21
 
22
- 3. Call the `check_multiple_dependencies` MCP tool (from maven-mcp server) with all extracted dependencies.
22
+ 3. Call the `compare_dependency_versions` MCP tool (from maven-mcp server) with ALL extracted dependencies including their current versions. The MCP server searches Maven Central, Google Maven, and Gradle Plugin Portal automatically — do NOT skip any dependencies based on their group ID.
23
23
 
24
24
  4. Present results as a markdown table:
25
25
 
@@ -34,3 +34,4 @@ Scan the current project for Maven/Gradle dependencies and report available upda
34
34
  - Always check `libs.versions.toml` first — it's the modern Gradle standard for version management.
35
35
  - Dependencies in `libs.versions.toml` may use version references in build files — resolve them.
36
36
  - Skip dependencies without explicit versions (e.g., BOM-managed or platform dependencies).
37
+ - **Send ALL dependencies to the MCP tool** — the server handles Google Maven, Gradle Plugin Portal, and custom repositories automatically. Do NOT filter, skip, or separate dependencies by group ID.