MCP server that resolves external Java/Kotlin classes from Gradle dependencies — returns artifact coordinates and class structure in one call.
MCP server that resolves external Java/Kotlin classes from Gradle dependencies — returns artifact coordinates and class structure in one call. Exposed over MCP by the gradle mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Model Context Protocol (MCP) server that lets AI agents look up external Java/Kotlin classes in a Gradle project in a single tool call — no more chains of find, grep, jar, and javap.
Everything the assistant can do here goes through one of these:
resolve_external_class — Resolve and inspect a class from external dependencies when you DON'T know which JAR contains it. Replaces manual find / grep / jar / javap chainsinspect_class — Same class structure as resolve_external_class, but takes a jarPath directly — skips Gradle classpath resolution. Use this when the JAR path islist_dependencies — List all resolved external dependencies across every source set's compile classpath (main + test + custom). Each entry includes sourceSets, e.gfind_dependency_version — Substring-match against group / artifact and return resolved versions. Case-insensitivedependency_insight — Wraps ./gradlew dependencyInsight --configuration compileClasspath --dependency . Returns the raw resolution chain and a parsed requestedBycheck_outdated — Compares resolved versions against the latest available on Maven Central and any other repositories the project declares — whether in a projectPATH (so javap is available) - The target project must have a Gradle wrapper (./gradlew on macOS/Linux, gradlew.bat on Windows) - macOS, Linux, or Windowsgradle-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gradle's toolset — resolve_external_class, inspect_class, list_dependencies and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| resolve_external_class | Resolve and inspect a class from external dependencies when you DON'T know which JAR contains it. Replaces manual find / grep / jar / javap chains. |
| inspect_class | Same class structure as resolve_external_class, but takes a jarPath directly — skips Gradle classpath resolution. Use this when the JAR path is already known (e.g. from a previous resolve_external_class result or list_de |
| list_dependencies | List all resolved external dependencies across every source set's compile classpath (main + test + custom). Each entry includes sourceSets, e.g. ["main"], ["test"], or ["main","test"]. |
| find_dependency_version | Substring-match against group / artifact and return resolved versions. Case-insensitive. |
| dependency_insight | Wraps ./gradlew dependencyInsight --configuration compileClasspath --dependency <query>. Returns the raw resolution chain and a parsed requestedBy list. |
| check_outdated | Compares resolved versions against the latest available on Maven Central **and** any other repositories the project declares — whether in a project repositories {} block or centrally in settings.gradle under dependencyRe |
Or, from a local checkout:
```json
{
"mcpServers": {
"gradle": {
"command": "node",
"args": ["/absolute/path/to/gradle-mcp-server/dist/index.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
PATH (so javap is available) - The target project must have a Gradle wrapper (./gradlew on macOS/Linux, gradlew.bat on Windows) - macOS, Linux, or WindowsKill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.