What the Javadocs MCP Server Solves for Java AI Development

When using AI tools to write code that depends on the Hutool library, developers may ask the AI which placeholder formats StrUtil.format supports. The AI confidently answers that {} works like SLF4J, but the code fails at runtime because Hutool only supports sequential replacement of {} and does not recognize indexed syntax.

The mismatch occurs because AI explores unfamiliar Java libraries via two unreliable methods: (1) online search of official docs, blogs, and Stack Overflow, which can return outdated information for libraries whose documentation lags behind code versions; and (2) bytecode decompilation with javap, which reveals method signatures but cannot show Javadoc comments that describe placeholder rules, null handling, or parameter length mismatches.

For example, the javap command

javap -classpath ~/.m2/repository/cn/hutool/hutool-core/5.8.44/hutool-core-5.8.44.jar \
  cn.hutool.core.util.StrUtil | grep "SLASH\|EMPTY\|SPACE"

shows the signature of StrUtil.format as

public static String format(CharSequence template, Object... params)

, but it cannot reveal that the Javadoc states the template uses {} for sequential placeholders only.

Java has a 30‑year tradition of embedding documentation in source code using /** ... */ comments, which the javadoc tool converts to HTML. In IntelliJ IDEA, pressing Ctrl+Q displays this documentation, and the generated HTML is published on sites like docs.spring.io. The Hutool Javadoc for StrUtil.format includes an example:

/**
 * Format text using {} as placeholders.
 * Example: format("this is {} for {}", "a", "b") → this is a for b
 * @param template text template, {} denotes replacement positions; if null, returns "null"
 * @param params parameter values
 * @return formatted text, or "null" if template is null
 */

which makes clear that only sequential replacement is supported.

All mainstream Java libraries (Hutool, Spring, MyBatis‑Plus, Guava, etc.) publish a -javadoc.jar alongside the binary JAR on Maven Central, but AI tools cannot directly access these archives.

The Javadocs MCP server ( javadocs.dev) provides an index service for Maven Central Javadocs, exposing a remote MCP endpoint at https://www.javadocs.dev/mcp. By connecting to this server, AI tools can retrieve full Javadoc content for any Maven Central library without installing local software. get_latest_version: query the latest version of any artifact on Maven Central. list_contents: list all packages, classes, and interfaces contained in a Javadoc JAR. get_symbol_content: obtain the complete Javadoc for a specific class or method.

The service supports both Java and Kotlin libraries, requires no authentication, and is free to use.

To enable Claude Code to use the MCP server, add the following command:

claude mcp add --transport sse javadocs https://www.javadocs.dev/mcp

Or edit the .claude/settings.json file manually:

{
  "mcpServers": {
    "javadocs": {
      "type": "sse",
      "url": "https://www.javadocs.dev/mcp"
    }
  }
}

Other CLI tools follow the same pattern—simply specify the MCP server URL.