Resolve JVM classpath via Gradle and extract Java source, signatures, and structure for agents (CLI + MCP)
Resolve JVM classpath via Gradle and extract Java source, signatures, and structure for agents (CLI + MCP)
When your agent hits an unfamiliar library type — say, a superclass from a proprietary internal library — it spends 25+ turns walking ~/.gradle/caches, opening JARs by hand with jar tf, picking one by guesswork, and trying to answer a question your IDE would answer in one keystroke: does this superclass have a public utility method called X?
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"jvmsrc": {
"command": "jvmsrc",
"args": [
"mcp"
]
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
NmapMCP is a robust integration of the Nmap scanning tool with the Model Context Protocol (MCP), enabling seamless network scanning capabilities
Every time an AI coding assistant edits a file, it normally needs two tool calls: one to Read the file, then one to Edit it. Refactoring across 5 files? That's 10 calls. Refactoring across 20?…
Guarded local Charles Proxy automation and bounded XML session evidence
Measured weekly data on Claude Code and coding agents: costs, plugins, MCP registry, npm, HN, issues