Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

JAIPilot

by JAIPilotversion 7.2.1i★ –iRuns in the cloud
Registry nameio.github.JAIPilot/jaipilot

Install

Overview

Description from the maker (original English)

Ship better Java with your coding agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://api.jaipilot.com/functions/v1/jaipilot/mcp

Run this in your terminal

claude mcp add --transport http jaipilot https://api.jaipilot.com/functions/v1/jaipilot/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://api.jaipilot.com/functions/v1/jaipilot/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account JAIPilot, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32403 servers in this category
  • Published to the registry more recently than 32% of the other 32403 servers in this category
  • Basic checks equal to or better than 100% of the other 32403 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is JAIPilot safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (7.2.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

LickityClick

by lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

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

Spring Petclinic — 100% coverage

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

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

Windows (PowerShell)

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

npm

npm install -g jaipilot

Homebrew (macOS / Linux)

brew install JAIPilot/tap/jaipilot

Sign in, then run inside your Java repository:

jaipilot auth login

jaipilot 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

jaipilot run generate_tests --class com.acme.OrderService

jaipilot run test_current_changes --all jaipilot 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:

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

The Maven adapter also provides local coverage checks and generation:

./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

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

Claude Code

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

Ask PopNx