Mcp Jacoco Reporter

Created By
crisschana year ago
Overview

What is MCP-JaCoCo?

MCP-JaCoCo is a server tool that converts JaCoCo code coverage reports into formats optimized for Large Language Models (LLMs), enhancing AI-driven analysis in software development.

How to use MCP-JaCoCo?

To use MCP-JaCoCo, install it using the provided configuration and run the jacoco_reporter_server to read JaCoCo XML reports and return coverage data in JSON format.

Key features of MCP-JaCoCo?

  • Smart conversion of JaCoCo XML reports into LLM-friendly JSON format.
  • Supports multiple coverage metrics (instruction, branch, line, etc.).
  • Fast and lightweight report processing.
  • Well-organized JSON output for easy AI consumption.
  • Customizable analysis by filtering coverage data.

Use cases of MCP-JaCoCo?

  1. Simplifying code coverage reports for AI analysis.
  2. Identifying untested or poorly tested code segments.
  3. Generating smart suggestions for new test cases.
  4. Streamlining AI-assisted test planning.
  5. Automating documentation of coverage results.

FAQ from MCP-JaCoCo?

  • Can MCP-JaCoCo handle all JaCoCo reports?

Yes! MCP-JaCoCo is designed to work with any JaCoCo XML report.

  • Is MCP-JaCoCo free to use?

Yes! MCP-JaCoCo is open-source and free for everyone.

  • How does MCP-JaCoCo improve testing workflows?

By converting complex XML reports into a structured JSON format, it allows for quicker analysis and better integration with AI tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
crisschan
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours ago
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