maven-central-mcp 0.2.4 → 0.2.5
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 +1 -1
- package/package.json +1 -1
- package/plugin/skills/check-deps/SKILL.md +17 -5
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.
|
|
14
|
+
version: "0.2.5",
|
|
15
15
|
});
|
|
16
16
|
let cachedRepos = null;
|
|
17
17
|
function getRepositories() {
|
package/package.json
CHANGED
|
@@ -14,24 +14,36 @@ Scan the current project for Maven/Gradle dependencies and report available upda
|
|
|
14
14
|
- `build.gradle.kts` or `build.gradle`
|
|
15
15
|
- `pom.xml`
|
|
16
16
|
|
|
17
|
-
2. Read the found files and extract
|
|
17
|
+
2. Read the found files and extract ALL dependencies with their current versions.
|
|
18
18
|
- For `libs.versions.toml`: parse the `[versions]` and `[libraries]` sections
|
|
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 `compare_dependency_versions` MCP tool
|
|
22
|
+
3. Call the `compare_dependency_versions` MCP tool with the extracted dependencies. Use the EXACT parameter format defined in the tool schema:
|
|
23
|
+
|
|
24
|
+
```json
|
|
25
|
+
{
|
|
26
|
+
"dependencies": [
|
|
27
|
+
{"groupId": "io.ktor", "artifactId": "ktor-client-core", "currentVersion": "3.1.2"},
|
|
28
|
+
{"groupId": "androidx.compose", "artifactId": "compose-bom", "currentVersion": "2025.05.00"}
|
|
29
|
+
]
|
|
30
|
+
}
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
Do NOT pass dependencies as a string. Do NOT add extra parameters like `stabilityFilter` or `includeSecurityScan` — they don't exist on this tool.
|
|
23
34
|
|
|
24
35
|
4. Present results as a markdown table:
|
|
25
36
|
|
|
26
37
|
| Artifact | Current | Latest | Upgrade |
|
|
27
38
|
|----------|---------|--------|---------|
|
|
28
|
-
| io.ktor:ktor-
|
|
39
|
+
| io.ktor:ktor-client-core | 3.1.2 | 3.1.3 | PATCH |
|
|
29
40
|
|
|
30
41
|
5. If all dependencies are up to date, say so.
|
|
31
42
|
|
|
32
43
|
## Important
|
|
33
44
|
|
|
34
45
|
- Always check `libs.versions.toml` first — it's the modern Gradle standard for version management.
|
|
35
|
-
- Dependencies in `libs.versions.toml` may use version references
|
|
46
|
+
- Dependencies in `libs.versions.toml` may use version references — resolve them to actual versions.
|
|
36
47
|
- Skip dependencies without explicit versions (e.g., BOM-managed or platform dependencies).
|
|
37
|
-
- **Send ALL dependencies to the MCP tool** — the server
|
|
48
|
+
- **Send ALL dependencies to the MCP tool** — the server searches Maven Central, Google Maven, and Gradle Plugin Portal automatically. Do NOT skip or filter any dependencies by group ID.
|
|
49
|
+
- **Use the exact tool schema** — pass `dependencies` as an array of objects with `groupId`, `artifactId`, `currentVersion` fields. No other format is accepted.
|