Skip to main content
Glama
adrianmikula

JakartaMigration

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.*).

Apify Store MCP Protocol

🚀 Quick Start

The easiest way to get started is using our hosted MCP server on Apify - no installation required!

Free Tier Available: Basic features are free. Get started →

MCP Server URL: https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP

Configuration Options:

Option A: Streamable HTTP (Recommended) - Simpler, more reliable:

{ "mcpServers": { "jakarta-migration": { "type": "streamable-http", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP" } } }

Option B: SSE (Legacy) - For clients that don't support Streamable HTTP yet:

{ "mcpServers": { "jakarta-migration": { "type": "sse", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP" } } }

💡 Why Streamable HTTP? Streamable HTTP is simpler, more reliable, and recommended by the MCP spec. SSE is deprecated but still supported for backward compatibility.

🔑 Authentication: You'll need an Apify API token. Get it from Apify Console → Integrations. Some MCP clients may prompt you to authenticate via OAuth.

See Apify Setup below for detailed instructions.

Option 2: Run Locally (STDIO)

For local development or when you need full control:

Prerequisites: Java 21+ and Node.js 18+

# Install via npm (one-time) npm install -g @jakarta-migration/mcp-server # Or use with npx (no installation) npx -y @jakarta-migration/mcp-server

See Local Setup below for client configuration.

📋 What It Does

The Jakarta Migration MCP Server enables your AI coding assistant to:

  • 🔍 Analyze Jakarta Readiness - Assess Java projects for migration readiness with detailed dependency analysis

  • 🚫 Detect Blockers - Identify dependencies and code patterns that prevent Jakarta migration

  • 📦 Recommend Versions - Suggest Jakarta-compatible versions for existing dependencies

  • 📋 Create Migration Plans - Generate comprehensive, phased migration plans with risk assessment

  • 📊 Analyze Migration Impact - Comprehensive impact analysis combining dependency analysis and source code scanning

  • ✅ Verify Runtime - Test migrated applications to ensure they run correctly after migration

The Problem It Solves

Migrating from Java EE 8 (javax.*) to Jakarta EE 9+ (jakarta.*) is complex because:

  • Dependency Hell: Many libraries haven't migrated, creating transitive conflicts

  • Binary Incompatibility: Compiled JARs may reference javax.* internally

  • Hidden Dependencies: javax.* usage in XML configs, annotations, and dynamic loading

  • Risk Assessment: Need to understand migration impact before starting

This MCP server provides AI assistants with the specialized knowledge and tools to navigate these challenges effectively.

🔒 Security & Privacy

Your code and project data are handled with the utmost care. We understand that Java developers working with enterprise codebases need complete confidence in the security and privacy of their intellectual property.

Stateless Architecture

No Data Persistence - The service is completely stateless. Your project files, source code, and analysis results are never stored, logged, or persisted on our servers.

No Data Collection - We don't collect, track, or analyze your code. Each request is processed independently with no memory of previous requests.

Local Execution Option - For maximum privacy, you can run the entire service locally using the Local Setup option. Your code never leaves your machine.

Privacy Guarantees

  • Zero Code Storage: Project files are only read during analysis and immediately discarded

  • No Telemetry: No usage tracking, analytics, or code scanning for any purpose other than migration analysis

  • Open Source: The core service is open source, so you can audit exactly what it does

  • Enterprise Ready: Safe for use with proprietary and sensitive codebases

Hosted Service (Apify)

When using the Apify-hosted service:

  • Analysis is performed in isolated, ephemeral containers

  • All containers are destroyed immediately after processing

  • No persistent storage is used

  • Your API token is only used for authentication and billing

Local Service

When running locally via STDIO:

  • 100% Local - Everything runs on your machine

  • No Network Calls - No external requests are made

  • Complete Control - You have full visibility and control over the process

For maximum security and privacy, we recommend using the local STDIO setup for sensitive projects.

💰 Pricing & Features

Free Tier (Community)

All core features included:

  • Dependency analysis

  • Blocker detection

  • Version recommendations

  • Migration planning

  • Runtime verification

Premium Features (Paid)

🚀 Advanced capabilities (coming soon):

  • Auto-Fixes - Automatically fix detected issues without manual intervention

  • One-Click Refactor - Execute complete Jakarta migration with a single command

  • Binary Fixes - Fix issues in compiled binaries and JAR files

  • Advanced Analysis - Deep transitive conflict detection and resolution

  • Batch Operations - Process multiple projects simultaneously

  • Custom Recipes - Create and use custom migration recipes

  • API Access - Programmatic API for CI/CD integrations

Pricing: Starting from $0.01 / 1,000 results. View pricing →

🔧 Setup Instructions

Apify Hosted Server Setup

The Apify-hosted server supports both Streamable HTTP and SSE transports.

MCP Server URL: https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP
Actor Page: apify.com/adrian_m/jakartamigrationmcp

🔑 Authentication Required: You'll need an Apify API token. Get it from Apify Console → Integrations. Some MCP clients support OAuth authentication which will prompt you to sign in.

💡 Transport Recommendation: Use Streamable HTTP (recommended) for better reliability and simplicity. SSE is available for backward compatibility but is deprecated in the MCP spec.

For Cursor IDE

⚠️ Important: Cursor primarily supports stdio transport, not SSE. For Cursor, use the Local Setup (STDIO) instructions below instead.

If your Cursor version supports HTTP transports:

  1. Open Cursor Settings (Ctrl+, on Windows/Linux or Cmd+, on Mac)

  2. Navigate to FeaturesMCP

  3. Click "+ Add New MCP Server"

  4. Add configuration (prefer Streamable HTTP):

Streamable HTTP (Recommended):

{ "mcpServers": { "jakarta-migration": { "type": "streamable-http", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } } } }

Or SSE (Legacy):

{ "mcpServers": { "jakarta-migration": { "type": "sse", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } } } }

🔑 Get API Token: Replace YOUR_APIFY_API_TOKEN with your token from Apify Console → Integrations

  1. Restart Cursor completely for changes to take effect

For Claude Code (VS Code Extension)

  1. Open VS Code Settings (Ctrl+, or Cmd+,)

  2. Search for "MCP" or navigate to ExtensionsClaude CodeSettings

  3. Add configuration (prefer Streamable HTTP):

Streamable HTTP (Recommended):

{ "mcpServers": { "jakarta-migration": { "type": "streamable-http", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } } } }

Or SSE (Legacy):

{ "mcpServers": { "jakarta-migration": { "type": "sse", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } } } }

🔑 Get API Token: Replace YOUR_APIFY_API_TOKEN with your token from Apify Console → Integrations

  1. Restart VS Code

For GitHub Copilot

GitHub Copilot supports MCP through the Copilot Chat interface:

  1. Open Copilot Chat (Ctrl+L or Cmd+L)

  2. Navigate to SettingsMCP Servers

  3. Add server:

    • URL: https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP

    • Transport Type: Streamable HTTP (recommended) or SSE (legacy)

    • Authorization: Add your Apify API token in the headers section

🔑 Get API Token: Get your token from Apify Console → Integrations

For Antigravity

  1. Open Antigravity Settings

  2. Navigate to MCP Configuration

  3. Add server (prefer Streamable HTTP):

Streamable HTTP (Recommended):

{ "name": "jakarta-migration", "type": "streamable-http", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } }

Or SSE (Legacy):

{ "name": "jakarta-migration", "type": "sse", "url": "https://mcp.apify.com/?tools=actors,docs,adrian_m/JakartaMigrationMCP", "headers": { "Authorization": "Bearer YOUR_APIFY_API_TOKEN" } }

🔑 Get API Token: Replace YOUR_APIFY_API_TOKEN with your token from Apify Console → Integrations

Local Setup (STDIO)

For local development, use STDIO transport which works with Cursor, Claude Code, and Antigravity.

Prerequisites

Installation

# Install globally (recommended) npm install -g @jakarta-migration/mcp-server # Or use with npx (no installation needed) npx -y @jakarta-migration/mcp-server

Configuration

Cursor IDE
  1. Open Cursor Settings (Ctrl+, or Cmd+,)

  2. Navigate to FeaturesMCP

  3. Add configuration:

Windows:

{ "mcpServers": { "jakarta-migration": { "command": "npx", "args": ["-y", "@jakarta-migration/mcp-server"] } } }

Mac/Linux:

{ "mcpServers": { "jakarta-migration": { "command": "npx", "args": ["-y", "@jakarta-migration/mcp-server"] } } }
  1. Restart Cursor completely

Claude Code (VS Code Extension)
  1. Open VS Code Settings

  2. Navigate to Claude CodeMCP Settings

  3. Add the same configuration as Cursor

  4. Restart VS Code

Antigravity
  1. Open Antigravity Settings

  2. Navigate to MCP Configuration

  3. Add:

{ "name": "jakarta-migration", "command": "npx", "args": ["-y", "@jakarta-migration/mcp-server"] }

Alternative: Run from JAR

If you've built the project locally:

Windows:

{ "mcpServers": { "jakarta-migration": { "command": "java", "args": [ "-jar", "C:\\path\\to\\jakarta-migration-mcp-1.0.0-SNAPSHOT.jar" ] } } }

Mac/Linux:

{ "mcpServers": { "jakarta-migration": { "command": "java", "args": [ "-jar", "/path/to/jakarta-migration-mcp-1.0.0-SNAPSHOT.jar" ] } } }

Local HTTP Setup (Streamable HTTP or SSE)

For local HTTP-based testing or development:

  1. Build the project:

    ./gradlew bootJar
  2. Start server with Streamable HTTP:

    java -jar build/libs/jakarta-migration-mcp-1.0.0-SNAPSHOT.jar \ --spring.profiles.active=mcp-streamable-http

    Or with SSE (legacy):

    java -jar build/libs/jakarta-migration-mcp-1.0.0-SNAPSHOT.jar \ --spring.profiles.active=mcp-sse
  3. Test the endpoint:

    # Streamable HTTP (recommended) curl -X POST http://localhost:8080/mcp/streamable-http \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' # Or SSE (legacy) curl -X POST http://localhost:8080/mcp/sse \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
  4. Configure MCP client to use http://localhost:8080/mcp/streamable-http (or /mcp/sse for SSE)

💬 Usage Examples

Once configured, you can use the MCP tools in your AI assistant:

Analyze Project Readiness

Analyze the Jakarta readiness of my project at /path/to/my-project

Detect Migration Blockers

Detect any blockers for Jakarta migration in my project

Get Version Recommendations

Recommend Jakarta-compatible versions for my dependencies

Create Migration Plan

Create a migration plan for migrating my project to Jakarta EE

Verify Runtime

Verify the runtime of my migrated application at /path/to/app.jar

🛠️ Available Tools

Tool

Description

analyzeJakartaReadiness

Comprehensive project analysis with readiness score

detectBlockers

Find dependencies and patterns that prevent migration

recommendVersions

Get Jakarta-compatible version recommendations

createMigrationPlan

Generate phased migration plan with risk assessment

analyzeMigrationImpact

Analyze full migration impact combining dependency analysis and source code scanning

verifyRuntime

Test migrated application execution

See MCP Tools Documentation for detailed tool descriptions and parameters.

🐛 Troubleshooting

Tools Not Appearing

  1. Restart your IDE completely - MCP servers load on startup

  2. Check MCP server status - Look for errors in IDE logs

  3. Verify configuration - Ensure JSON syntax is correct

  4. Check prerequisites - Java 21+ and Node.js 18+ must be installed

Connection Issues

For Apify (SSE):

  • Verify your internet connection

  • Check if Apify service is available

  • Ensure you're using the correct URL

For Local (STDIO):

  • Verify Java is installed: java -version

  • Verify Node.js is installed: node --version

  • Try running manually: npx -y @jakarta-migration/mcp-server

Platform-Specific Issues

Windows:

  • Use forward slashes in paths: C:/path/to/file.jar

  • Ensure Java is in your PATH

Mac/Linux:

  • Ensure execute permissions: chmod +x gradlew

  • Use absolute paths in configuration

📚 Documentation

For Users

For Developers

🔗 Resources

📄 License

MIT License - See LICENSE file for details.

🙏 Acknowledgments

Built with ❤️ for the Java community. Special thanks to:

  • Spring AI team for MCP framework

  • OpenRewrite for migration recipes

  • Apify for hosting infrastructure


Need help? Open an issue or check our documentation.

-
security - not tested
F
license - not found
-
quality - not tested

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrianmikula/JakartaMigration'

If you have feedback or need assistance with the MCP directory API, please join our Discord server