Javadoc Mcp

Created By
BeamLiu7 months ago
Overview

What is Javadoc Mcp?

Javadoc Mcp is a comprehensive solution for generating structured JSON documentation from Java source code and providing intelligent search capabilities through the Model Context Protocol (MCP).

How to use Javadoc Mcp?

To use Javadoc Mcp, you need to integrate the Maven plugin into your Java project to generate JSON documentation, and then start the MCP server to enable intelligent search functionalities.

Key features of Javadoc Mcp?

  • Generates structured JSON documentation from Java source code.
  • Provides intelligent search capabilities for the generated documentation.
  • Supports crawling documentation from HTML Javadoc websites.
  • Integrates with Claude Desktop for enhanced AI assistance.

Use cases of Javadoc Mcp?

  1. Generating JSON documentation for Java libraries.
  2. Enabling intelligent search for large Java codebases.
  3. Assisting developers in finding documentation quickly through AI integration.

FAQ from Javadoc Mcp?

  • Can Javadoc Mcp generate documentation for all Java versions?

Currently, it supports Java 8 and above, with future versions planned for support.

  • Is Javadoc Mcp free to use?

Yes! Javadoc Mcp is open-source and free to use.

  • How do I start the MCP server?

You can start the MCP server using the command: npx @io.emop/mcp-javadoc-server --javadoc-path /path/to/javadoc-json.

Server Config

{
  "mcpServers": {
    "javadoc-search": {
      "command": "npx",
      "args": [
        "-y",
        "@io.emop/mcp-javadoc-server",
        "--javadoc-path",
        "/absolute/path/to/javadoc-json"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
BeamLiu
Star
-
Language
-
License
-

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