MCP.so
ログイン
J

Jakarta Migration MCP Server

@adrianmikula

基本情報

カテゴリ

その他

トランスポート

stdio

作者

adrianmikula

投稿者

Adrian

Jakarta Migration MCP Server について

A Model Context Protocol (MCP) server that provides AI coding assistants with specialized tools for analyzing and migrating Java applications from Java EE 8 (javax.*) to Jakarta EE 9+ (jakarta.*).

#java#javax#jakarta#tomcat#tomee#jboss#websphere#glassfish

Jakarta Migration MCP Server の設定

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

{
  "mcpServers": {
    "jakarta-migration": {
      "type": "sse",
      "url": "http://localhost:8080/mcp/sse"
    }
  }
}

Jakarta Migration MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

What is Jakarta Migration Mcp?

Jakarta Migration Mcp is a Model Context Protocol (MCP) server that provides AI coding assistants with specialized tools for analyzing and migrating Java applications from Java EE 8 (javax.*) to Jakarta EE 9+ (jakarta.*). It is designed for developers and teams undertaking Jakarta EE migration projects.

How to use Jakarta Migration Mcp?

Install via npm (npm install -g @jakarta-migration/mcp-server) or use npx -y @jakarta-migration/mcp-server. Requires Java 21+ and Node.js 18+. Configure your MCP client (e.g., Cursor, Claude Code) with the command npx -y @jakarta-migration/mcp-server. Run locally via STDIO for maximum privacy, or optionally via Streamable HTTP/SSE.

Key features of Jakarta Migration Mcp

  • Analyze Jakarta readiness with detailed dependency analysis
  • Detect blockers that prevent Jakarta migration
  • Recommend Jakarta-compatible versions for dependencies
  • Generate comprehensive, phased migration plans
  • Analyze full migration impact combining dependency and source scanning
  • Verify migrated applications run correctly after migration

Use cases of Jakarta Migration Mcp

  • Assess a legacy Java EE 8 project for Jakarta migration readiness
  • Identify conflicting dependencies and hidden javax.* references
  • Create a step-by-step migration plan with risk assessment
  • Validate that a migrated application works after the transition

よくある質問

1

What does Jakarta Migration Mcp do that a simple search/replace cannot?

It handles complex migration challenges like dependency conflict resolution, analysis of compiled JARs, and detection of `javax.*` usage in XML configs, annotations, and dynamic loading – tasks far beyond simple text substitution.

2

What are the runtime requirements?

Java 21+ and Node.js 18+ are required. The server is a stateless Java application that runs locally; no external services are needed for STDIO mode.

3

Is my source code stored or transmitted when using this server?

No. The server is completely stateless – project files are read only during analysis and immediately discarded. For maximum privacy, use the local STDIO setup so your code never leaves your machine.

4

What transport options does Jakarta Migration Mcp support?

It supports STDIO (local, recommended) and optional HTTP transports: Streamable HTTP (recommended for HTTP) and legacy SSE.

5

Are there any known limitations or dependencies?

The server only analyzes projects that use the Maven/Gradle build system with Java source code. It does not support all build tools, and dynamic class loading may still require manual inspection.

コメント

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