MCP.so
ログイン

Descartes Java REPL and Deep Introspection For Your Java Apps

@widoriezebos

Descartes Java REPL and Deep Introspection For Your Java Apps について

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.

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

widoriezebos

投稿者

Wido

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "morpheus": {
      "command": "node",
      "args": [
        "/path/to/mcp/mcp-tcp-adapter.js"
      ],
      "env": {
        "MCP_HOST": "localhost",
        "MCP_PORT": "9080",
        "MCP_DEBUG": "false",
        "MCP_RECONNECT_MIN_DELAY": "500",
        "MCP_RECONNECT_MAX_DELAY": "5000",
        "MCP_HEALTH_CHECK_INTERVAL": "5000",
        "MCP_LOG_RATE_LIMIT_WINDOW": "60000",
        "MCP_LOG_RATE_LIMIT_MAX": "10"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Descartes Java REPL and Deep Introspection For Your Java Apps?

Descartes Java REPL and Deep Introspection For Your Java Apps is a Java‑based Model Context Protocol (MCP) server that provides deep introspection, monitoring, debugging, and a JShell REPL for Java applications. It enables AI assistants to interact with running Java processes through a comprehensive set of tools and resources.

How to use Descartes Java REPL and Deep Introspection For Your Java Apps?

Clone the repository, build with mvn clean package, and run the example server with mvn exec:java. Connect an MCP client via the included TCP adapter (config/mcp/mcp-tcp-adapter.js) and configure it in your client’s JSON configuration. The server listens on port 9080 by default.

Key features of Descartes Java REPL and Deep Introspection For Your Java Apps

  • JShell REPL for interactive Java code execution
  • Object Inspector for deep object introspection
  • Process and system monitoring with real‑time metrics
  • Thread analyzer with deadlock detection
  • Memory analyzer (heap, GC, memory pools)
  • Exception analysis and Log4j2 log integration

Use cases of Descartes Java REPL and Deep Introspection For Your Java Apps

  • Debugging and inspecting live Java applications in development
  • Monitoring JVM/system metrics and thread health
  • Analyzing exceptions and log captures
  • Executing arbitrary Java code via REPL for testing
  • Accessing application context objects and JMX MBeans

FAQ from Descartes Java REPL and Deep Introspection For Your Java Apps

Is the JShell REPL safe to use in production?

No. The REPL allows arbitrary code execution with full JVM permissions. It should only be used in development/debugging environments and never exposed to untrusted networks or users.

What are the runtime requirements?

Java 16 or higher (compiled with Java 23), Maven 3.6+, and Node.js for the TCP adapter.

Where does the data live?

All introspection data and REPL sessions live inside the target JVM process. Application objects are accessible via a context map; resources provide read‑only views of system state.

How does Descartes communicate?

The server uses JSON‑RPC 2.0 over TCP sockets. Each client connection runs in a separate thread for concurrent operation.

Are there any authentication or access controls?

The README recommends restricting access to localhost only, and warns against exposing the server beyond trusted networks. No built‑in authentication layers are described.

コメント

「その他」の他のコンテンツ