JAIPilot

Name: JAIPilot
Author: JAIPilot

作者：JAIPilot版本 7.2.1i★ –i在云端运行

注册名称io.github.JAIPilot/jaipilot

安装

概览

作者提供的说明（英文原文）

Ship better Java with your coding agent.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://api.jaipilot.com/functions/v1/jaipilot/mcp

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://api.jaipilot.com/functions/v1/jaipilot/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 JAIPilot 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32433 个服务器的 0%
发布到注册中心的时间比此分类中其他 32433 个服务器的 32% 更新
基础检查结果等于或优于此分类中其他 32433 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

JAIPilot 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（7.2.1）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

Symantec Cloud DLP AIops

作者：AIops-tools

Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

Inspect your code, build, and test framework.
Generate or repair tests for behavior, boundaries, and failure paths, with meaningful assertions.
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.

Outcome	Workflow
Generate unit tests	`generate_tests`
Improve coverage	`improve_coverage`
Fix failing tests	`fix_tests`
Stabilize flaky tests	`stabilize_flaky_tests`
Test current changes	`test_current_changes`
Lock behavior before a refactor	`lock_behavior`
Target 100% line coverage	`coverage_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

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 suite	Codex alone	Codex + JAIPilot
Passing JUnit tests	3	16
Line coverage of the selected `Deadline` class	47.1%	100%
Line coverage across both fixture classes	40%	65.7%
Branch coverage across both fixture classes	30%	80%
Injected faults caught by the saved tests	3/10	7/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.

Lock: lock_behavior creates and runs characterization tests before production edits, targeting 90%+ line coverage when configured.
Edit: Your coding agent changes production code. Baseline tests stay unchanged.
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