JAIPilot

io.github.JAIPilotPublished by GitHub account JAIPilotv7.2.1Updated Oct 24, 2026

Ship better Java with your coding agent.

The publisher's own server: QuickBooks Connector by Meridian

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

JAIPilot is a Java testing service that lets a coding agent generate, repair and verify unit tests and raise line coverage in a Java repository.

What you can do
Generate, repair and stabilize unit tests for selected classes, paths or lines, with meaningful assertions and failure-path coverage (generate_tests, fix_tests, stabilize_flaky_tests). Raise measured line coverage toward a 90%+ target, including a 100% coverage workflow (improve_coverage, coverage_100). Test only the current changes, or lock existing behavior with characterization tests before a refactor and verify the baseline afterwards (test_current_changes, lock_behavior, verify_behavior). Inspect the project's code, build and test framework, then run focused tests, the regression suite and fresh coverage reports.
When to use it
Useful when a coding agent works on a Java codebase and you want faster, higher-coverage test generation than the agent produces alone, or a behavior baseline to protect before refactoring. It is optional tooling layered onto an existing agent rather than a replacement for it.
Requirements
A JAIPilot account with subscription and credits, signed in through the CLI. Git, a JDK and the project's build tools; a build that includes the mcp command, launched with the repository path. Tests and commands run locally; the service is reached over the network.
Before you install
Selected source, project context and command output are sent to JAIPilot's managed service and a model provider. Workflows modify test files in your repository, so review the result and git diff before accepting changes. Usage consumes JAIPilot credits, and local commands have a default one-hour timeout.

Installation

In SourceWeft

  1. Open JAIPilot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.JAIPilot%2Fjaipilot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jaipilot": {
      "type": "http",
      "url": "https://api.jaipilot.com/functions/v1/jaipilot/mcp"
    }
  }
}

README

[JAIPilot]

JAIPilot — faster Java testing, stronger coverage, fewer bugs

Make your tests bulletproof.
~5× faster testing.
Enterprise grade unit tests. A 90%+ line coverage target.

Your Java testing specialist—straight from the terminal. Generate, repair, and verify tests. Fewer prompts. Stronger assertions.

Optimized for outcomes. Choose an outcome. Select your code. Get verified tests. Start with the CLI. Add MCP when you want JAIPilot inside your coding agent.

Download CLI · Get started · MCP setup · JAIPilot.com

See it run

Apache Kafka

[Actual Terminal recording of JAIPilot improving Apache Kafka's Deadline and LockUtils tests from 34.3% to 97.1% line coverage]

34.3% → 97.1% line coverage for two classes in 1m 53s. Added 13 tests; all 949 module tests passed.

Spring Petclinic — 100% coverage

[Actual Terminal recording of JAIPilot's coverage_100 workflow on Spring Petclinic, from 85.7% to 100% line coverage in 3m 21s]

85.7% → 100% line coverage across the project in 3m 21s. Added 36 tests with coverage_100; all 111 tests passed.

Production code preserved. Actual Terminal recordings; GIFs shorten idle waits. Reported times are full job durations with warm build caches; results vary. Commands, recordings, and full measurements →

How it works

Frontier LLM reasoning. Optimized testing tools. Prompts tailored to each outcome. Parallel workers in the managed service. Independent class tasks can run concurrently; local execution uses your toolchain and supported hardware parallelism.

  1. Inspect your code, build, and test framework.
  2. Generate or repair tests for behavior, boundaries, and failure paths, with meaningful assertions.
  3. Verify with focused tests, the final regression suite, and fresh coverage reports when configured.

90%+ line coverage target for generate_tests, improve_coverage, and lock_behavior, measured in selected production code when coverage is configured. Gaps and blockers are reported. Behavior baselines must pass before edits.

OutcomeWorkflow
Generate unit testsgenerate_tests
Improve coverageimprove_coverage
Fix failing testsfix_tests
Stabilize flaky testsstabilize_flaky_tests
Test current changestest_current_changes
Lock behavior before a refactorlock_behavior
Target 100% line coveragecoverage_100

Install

Requires Git, a JDK, and your project's build tools.

macOS / Linux

bash
curl -fsSL https://raw.githubusercontent.com/JAIPilot/jaipilot/main/install.sh | sh

Windows (PowerShell)

powershell
irm https://github.com/JAIPilot/jaipilot/releases/latest/download/install.ps1 | iex

npm

bash
npm install -g jaipilot

Homebrew (macOS / Linux)

bash
brew install JAIPilot/tap/jaipilot

Sign in, then run inside your Java repository:

bash
jaipilot auth loginjaipilot run improve_coverage --class com.acme.OrderService

Same JAIPilot account, subscription, and credits. Automatic update checks before workflows.

Install paths, manual updates, and troubleshooting →

Use the CLI

bash
jaipilot run generate_tests --class com.acme.OrderServicejaipilot run test_current_changes --alljaipilot run lock_behavior --path src/main/java/com/acme

Scope: whole repository, classes, paths, or selected lines. Review the result and git diff before accepting changes.

For a fresh, verified coverage target on a single-module Maven project:

bash
jaipilot run improve_coverage --all --coverage-target 80

The Maven adapter also provides local coverage checks and generation:

bash
./mvnw com.jaipilot:jaipilot-maven-plugin:1.2.1:check -Djaipilot.coverage.line=80./mvnw com.jaipilot:jaipilot-maven-plugin:1.2.1:run -Djaipilot.coverage.line=80

The Maven adapter 1.2.1 is published on Maven Central. Use mvnw.cmd in Windows PowerShell. Adapter setup, class/branch targets, and supported JaCoCo rules →

All commands, scopes, JSON output, and exit codes →

Why use JAIPilot if my coding agent already writes tests?

Fast testing. High coverage. Stronger tests. Less work for your coding agent.

  • ~5× faster testing than a general coding agent. Optimized prompts, tools, and parallel workers carry the testing workflow. Actual runtime varies by project. CLI examples: 97.1% coverage in 1m 53s on Kafka; 100% in 3m 21s on Petclinic.
  • 90%+ line coverage target. Meaningful assertions for selected behavior, boundaries, and failure paths, measured with your configured coverage tools.
  • Stronger regression protection. Lock behavior before edits; verify the original tests afterward. Our paired Codex example's saved tests caught 7/10 injected faults vs 3/10 with Codex alone.
  • Token efficiency. Offload test planning, generation, and repairs to JAIPilot's optimized service. This can reduce your coding agent's testing context, token use, and costs; JAIPilot credits apply.

Measured example: Codex with JAIPilot

Same refactor. Two fresh Codex sessions. Two Kafka utility classes. The MCP session used JAIPilot automatically, with no repository instruction file or extra testing prompt.

Saved regression suiteCodex aloneCodex + JAIPilot
Passing JUnit tests316
Line coverage of the selected Deadline class47.1%100%
Line coverage across both fixture classes40%65.7%
Branch coverage across both fixture classes30%80%
Injected faults caught by the saved tests3/107/10

13 more reusable tests. Four more deliberately introduced bugs caught. Same model, settings, initial tests, and warm build caches. One paired example; results vary.

The 90% target applies to selected code. Deadline: 100% (17/17 lines). The combined 65.7% (23/35) includes untargeted LockUtils, unchanged at 6/18 covered lines.

Method, evidence, and reproduction →

MCP for coding agents

Optional: make Codex, Claude Code, or another MCP agent better at Java testing. Give it a tested baseline before edits and real failures to guide repairs.

  1. Lock: lock_behavior creates and runs characterization tests before production edits, targeting 90%+ line coverage when configured.
  2. Edit: Your coding agent changes production code. Baseline tests stay unchanged.
  3. Verify: verify_behavior reruns the original baseline. Your agent investigates failures and repairs unintended changes before finishing.

Passing tests protect the behavior they exercise. Review old expectations for intentional behavior changes.

Codex

bash
codex mcp add jaipilot -- jaipilot mcp --repo /absolute/path/to/java-repository

Claude Code

bash
claude mcp add --transport stdio jaipilot -- jaipilot mcp --repo /absolute/path/to/java-repository

Start a new agent session. MCP instructions and tool descriptions include the workflow. No repository instruction file required. Tests and commands run locally. Jobs run in the background; 1 hour per local command by default.

Requires a build with the mcp command. Source setup, tool contracts, and timeout options →

Local execution and privacy

Builds and tests run locally. Selected source, project context, and command output go to JAIPilot's managed service and model provider. Sign-in credentials stay local with user-only permissions.

Privacy details · Ask a question · Report an issue · Report a vulnerability privately

MIT License · JAIPilot.com

Source: README.md at commit d3fc8bc

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v7.2.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Pilot integrations