Descartes Java REPL and Deep Introspection For Your Java Apps

MCP其他

提供方 widoriezebos

其他 未标注 会话登录 社区 / 第三方 Claude DesktopClaudeCursorCodex

A Java-based Model Context Protocol (MCP) server that provides deep introspection, monitoring, debugging, and REPL capabilities for Java applications. Descartes enables AI assistants to interact with running Java processes through a comprehensive set of tools and resources.

一句话选型结论

按资料字段整理

Descartes Java REPL and Deep Introspection For Your Java Apps 属于其他类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

java jvm debugging introspection

支持客户端

适用场景

javajvmdebugging

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Descartes Java REPL and Deep Introspection For Your Java Apps当前 未标注 未标注 未标注 无 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方widoriezebos上游标注的维护方 widoriezebos
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

7.3 KB
来自项目仓库与上游目录的原文,未做删改

Descartes MCP

Debug live JVMs from MCP clients such as Claude Code, Codex, and Gemini CLI.

Descartes has two operating modes:

  • Proxy mode for external debugging against JDWP-enabled JVMs.
  • Embedded mode for full in-process runtime tooling (JShell, profiler, hot reload, resources, and more).

> Security: run only in trusted development/test environments. JDWP and debugger tools can inspect memory, evaluate code, and suspend application threads.


Why You Should Use Descartes

  • Debug JDWP-enabled JVMs without restarting application code.
  • Investigate blocked and waiting execution paths with debugger thread/stack tools (debugger_threads, debugger_stacktrace).
  • Share a repeatable debugging workflow with AI-assisted agent tooling.
  • Move from proxy-first debugging to embedded, full-runtime introspection when needed.

Try It

Prerequisites: JDK 17+, Maven 3+, Node.js.

Pick a scenario below. Both use the included BuggyCalculator example app, which contains six intentional bugs (off-by-one, NPE, integer overflow, wrong conditional, edge-case handling, swapped business logic).

> First check MCP registration below; that needs to be done before you try one of the scenarios below
>

Scenario A -- Agent does everything (unattended)

The agent builds, launches, connects, and debugs without manual intervention. You only type the prompt.

Step 1 -- Start the proxy in a separate terminal```bash
./scripts/run-remote-proxy-from-maven.sh


Exposes MCP on port `9090`, configured to reach JDWP on `localhost:5005` (the actual JDWP connection happens later, when the agent starts a debug session). By default it uses the version from `pom.xml`; pass `--version ` to pin a specific release artifact.

For local source builds during development, use `./scripts/run-remote-proxy.sh` instead.

**Step 2 -- Ask the agent to debug**

Open Claude Code, Codex, or Gemini CLI from this repo and paste:

> Build with `mvn clean package -DskipTests`, launch
> `com.bitsapplied.descartes.example.debugger.DebuggerWorkflowExample`
> with JDWP in `--interactive` mode, then find the six bugs in
> `com.bitsapplied.descartes.example.debugger.scenarios.BuggyCalculator`.

The debug skill handles launch mechanics (script, JDWP flags, port). The agent connects and steps through all six bugs autonomously.

The checked-in client configurations are pre-configured for the proxy. No additional MCP or skill installation is needed in this repository.

### Scenario B -- You launch the app, agent connects

You start the target app yourself (useful when reproducing a specific state, or when the app requires manual setup). The agent only attaches and debugs.

**Step 1 -- Build the JAR (once)**```bash
mvn clean package -DskipTests

Step 2 -- Start the proxy in a separate terminal```bash
./scripts/run-remote-proxy-from-maven.sh


**Step 3 -- Launch the example app with JDWP in another terminal**```bash
mkdir -p .pids
scripts/launch-managed-nontty.sh \
  --name buggy-calc \
  -- java \
     -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=localhost:5005 \
     -cp target/descartes-mcp-*-jar-with-dependencies.jar \
     com.bitsapplied.descartes.example.debugger.DebuggerWorkflowExample \
     --interactive </dev/null 2>&1 | tee .pids/buggy-calc.log

Wait for Listening for transport dt_socket at address: 5005 before continuing.

launch-managed-nontty.sh requires non-TTY file descriptors. The &1 | tee redirection satisfies that: stdin comes from /dev/null, stderr merges into stdout, and the pipe to tee makes stdout non-TTY while still printing to your terminal.

Step 4 -- Ask the agent to debug

Open Claude Code, Codex, or Gemini CLI from this repo and ask:

> The BuggyCalculator app is already running with JDWP on port 5005. Connect the debugger and find the bugs in BuggyCalculator.

The agent will connect to the existing JDWP session and debug without trying to launch anything.

Step 5 -- Clean up when done

Stop the app using the PID file:```bash
kill "$(cat .pids/buggy-calc.pid)"


### MCP registration

This checkout includes native project configuration for each supported client:

| Client | MCP configuration | Skill discovery |
| --- | --- | --- |
| Claude Code | `.mcp.json` | `.claude/skills/descartes-debug` symlink |
| Codex | `.codex/config.toml` | Canonical `.agents/skills/descartes-debug` |
| Gemini CLI | `.gemini/settings.json` | Canonical `.agents/skills/descartes-debug` |

All three configurations launch `config/mcp/mcp-tcp-adapter.js` against MCP port `9090` with long debugger waits enabled. Start the proxy, open the client from this repository, and use the `descartes-debug` skill—there is no user-global skill install step.

### Debug your own app

Start your app with JDWP and ask the agent to connect:```bash
java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=localhost:5005 -jar your-app.jar

Use address=*:5005 to listen on all interfaces (remote debugging). If your shell is zsh, quote the flag to prevent glob expansion: '-agentlib:jdwp=...,address=*:5005'.

Debug skill (recommended for agents)

Copy the canonical skill into your target project for structured debugging workflows, then add Claude's discovery symlink:```bash
mkdir -p .agents/skills .claude/skills
cp -R /path/to/descartes-mcp/.agents/skills/descartes-debug .agents/skills/
ln -s ../../.agents/skills/descartes-debug .claude/skills/descartes-debug


Codex and Gemini discover `.agents/skills` directly. See doc/debug-skill.md for validation and Windows guidance.

---

## How It Fits

Proxy mode:```mermaid
flowchart LR
  A[Claude Code / Codex / Gemini] <--> B[mcp-tcp-adapter.js]
  B <--> C[Descartes MCP Proxy]
  C <--> D[Target JVM via JDWP]

Embedded mode:```mermaid
flowchart LR
A["Claude Code / Codex / Gemini"] <--> B["mcp-tcp-adapter.js"]

subgraph APP["Your app JVM"]
C1["MCPServer + Descartes tools/resources + shared application context"]
end

B <--> C1
```

Use proxy mode when you want external, agent-driven inspection via JDWP.
Use embedded mode when you want full Descartes capabilities in-process.


Modes: Which One To Start With

Path Setup Best for
Proxy mode Minutes Debugging existing JDWP-enabled JVMs with no application code changes
Embedded mode Requires dependency changes JShell, profiling, hot reload, and deeper introspection

Known Restriction

One proxy instance can target one JVM at a time. For multi-JVM workflows, run one proxy per target JVM or pick different ports.

See doc/restrictions.md.


Quick Tips

  • Stop cleanly: end MCP usage, stop proxy with Ctrl+C, then stop target JVM.
  • Port setup: keep adapter MCP port (MCP_PORT) aligned with proxy --mcp-port. Configure JDWP host/port separately for the target JVM.
  • For agent-launched targets, use non-TTY launch and include the same JDWP flag used in manual startup.
  • For JDK 21+ virtual-thread targets, add includevirtualthreads=y to the target JVM's JDWP flag when you need virtual threads to appear in thread-list snapshots.
  • When debugging Descartes itself, set DESCARTES_FORCE_PLATFORM_THREADS=true or -Dtools.executor.virtualThreads.enabled=false to run shared tool tasks on bounded platform threads.

Learn More

  • doc/quick-start.md
  • doc/adapter.md
  • doc/debugger.md
  • doc/how-to-embed.md
  • doc/debug-skill.md
  • doc/restrictions.md

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Descartes Java REPL and Deep Introspection For Your Java Apps 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Descartes Java REPL and Deep Introspection For Your Java Apps 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Descartes Java REPL and Deep Introspection For Your Java Apps 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Descartes Java REPL and Deep Introspection For Your Java Apps 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Descartes Java REPL and Deep Introspection For Your Java Apps 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Descartes Java REPL and Deep Introspection For Your Java Apps 能提供哪些能力?

资料显示能力标签包括 java、jvm、debugging、introspection。具体工具清单以官方文档为准。

Descartes Java REPL and Deep Introspection For Your Java Apps 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。