Javadoc Mcp

Created By
loong953 months ago
让 AI 助手能够通过 Maven 坐标浏览 JavaDoc 文档
Overview

javadoc-mcp

一个 MCP (Model Context Protocol) 服务器,让 AI 助手能够通过 Maven 坐标浏览 JavaDoc 文档。

功能

提供 5 个 MCP tools,支持逐层浏览 JavaDoc:

Tool说明
list_packages列出库中所有包
list_classes列出包中所有类、接口、枚举、注解
get_class获取类概览文档(签名、描述、成员摘要)
get_member获取方法/字段的完整文档(参数、返回值、异常等)
search按关键词搜索类型、成员或包

运行要求

  • Node.js 18+
  • Maven (mvn 需要在 PATH 中可用)

服务会优先读取本地 Maven 仓库中的 JavaDoc JAR;如果缺失,则通过 mvn dependency:get 拉取对应的 -javadoc.jar

安装

方式一:直接通过 npx 使用

npx -y javadoc-mcp

方式二:全局安装

npm install -g javadoc-mcp

安装完成后,可直接运行:

javadoc-mcp

配置 MCP 客户端

Claude Code

推荐直接通过 npx 启动,这样不需要手动管理安装路径:

编辑 ~/.claude/settings.json

{
  "mcpServers": {
    "javadoc": {
      "command": "npx",
      "args": ["-y", "javadoc-mcp"]
    }
  }
}

如果你已经全局安装,也可以写成:

{
  "mcpServers": {
    "javadoc": {
      "command": "javadoc-mcp",
      "args": []
    }
  }
}

Claude Desktop

编辑 claude_desktop_config.json

{
  "mcpServers": {
    "javadoc": {
      "command": "npx",
      "args": ["-y", "javadoc-mcp"]
    }
  }
}

从源码开发

npm install
npm run build

构建产物输出到 dist/ 目录。

调试

使用 MCP Inspector 进行交互式测试:

npx @modelcontextprotocol/inspector node dist/index.js

使用示例

典型的浏览流程:

1. list_packages(groupId="org.apache.commons", artifactId="commons-lang3", version="3.14.0")
   → 获取所有包名

2. list_classes(..., packageName="org.apache.commons.lang3")
   → 查看包中的类列表

3. get_class(..., className="org.apache.commons.lang3.StringUtils")
   → 查看 StringUtils 类的概览和方法摘要

4. get_member(..., className="org.apache.commons.lang3.StringUtils", memberName="join")
   → 查看 join 方法的完整文档

5. search(..., query="String", category="type")
   → 搜索名称含 "String" 的类型

本地仓库

JavaDoc JAR 直接使用 Maven 本地仓库中的文件,默认路径为 ~/.m2/repository。如果 ~/.m2/settings.xml 中配置了 <localRepository>,则使用该路径。

如需重新拉取某个文档,可删除对应坐标下的 *-javadoc.jar 后再次调用工具。

技术栈

  • TypeScript (ES Modules)
  • @modelcontextprotocol/sdk — MCP 协议实现
  • cheerio — HTML 解析
  • adm-zip — 直接从 JAR 读取文件,不解压到磁盘
  • zod — 参数校验

Server Config

{
  "mcpServers": {
    "javadoc": {
      "command": "npx",
      "args": [
        "-y",
        "javadoc-mcp"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
loong95
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago