FastMCP FastMCP
Sign In
J

Jakarta Migration

Remote Remote

Automates Java EE to Jakarta EE migrations with dependency analysis, namespace refactoring from java...

4 views
0 installs
Updated Jan 17, 2026
Not audited
Developer Tools Coding
Tools I Recommend
ShipFast ShipFast Sponsor RunPod RunPod Sponsor
Automates Java EE to Jakarta EE migrations with dependency analysis, namespace refactoring from javax.* to jakarta.* packages, and runtime compatibility verification using OpenRewrite recipes.

HTTP HEADERS — Apify (Apify-hosted MCP server, required)

  1. Sign in to Apify:
    1. Open the Apify Console (Apify account → Integrations).
    2. If you don’t have an account, create one and sign in.
  2. Open Integrations / API tokens:
    1. In the Apify Console, navigate to the Integrations or API tokens section.
  3. Create a new API token:
    1. Click the button to create/generate a new API token.
    2. Give it a descriptive name (e.g., "FastMCP Integration").
    3. Choose the minimum scopes/permissions needed (or default/full for testing).
  4. Copy and securely store the token:
    1. Copy the token when it is displayed (it may only be shown once).
    2. Store it in a secure place (password manager) — do not share it publicly.
  5. Format the header for FastMCP:
    1. Header name: Authorization
    2. Header value (exact format required): Bearer YOUR_APIFY_API_TOKEN
      • Replace YOUR_APIFY_API_TOKEN with the token you copied.
      • Include the literal prefix "Bearer " (with the space).
  6. Fill the header in the FastMCP connection interface:
    1. Click the "Install Now" button to open the FastMCP connection interface.
    2. Under HTTP Headers, add:
    • Key: Authorization
    • Value: Bearer YOUR_APIFY_API_TOKEN
    1. Save the configuration.
  7. Restart your MCP client (IDE / extension) if required (e.g., Cursor, VS Code, etc.) so the new server/auth is loaded.

ENVIRONMENT VARIABLES — Local (optional; for STDIO or local JAR runs)

  1. Determine whether you need any env vars:
    1. Apify-hosted use: no environment variables required for the hosted MCP endpoint.
    2. Local STDIO / local JAR use: you may set optional vars below.
  2. Common local env vars and what to set:
    1. JAKARTA_MCP_JAR_PATH — (optional) path to a locally built JAR if you want the wrapper to use your local build. Example value: /path/to/jakarta-migration-mcp-1.0.0-SNAPSHOT.jar
    2. (Premium) jakarta-migration-license.json location — if you need to enable premium features, place your license file at:
    • Linux/macOS: ~/.mcp-settings/jakarta-migration-license.json
    • Windows: %USERPROFILE%.mcp-settings\jakarta-migration-license.json
  3. Add env vars in FastMCP:
    1. Click the "Install Now" button to open the FastMCP connection interface.
    2. Under Environment Variables (or ENVs), add each name/value pair:
    • Example: Key: JAKARTA_MCP_JAR_PATH Value: /full/path/to/jakarta-migration-mcp-1.0.0-SNAPSHOT.jar
    • Example (optional license): Key: JAKARTA_MCP_LICENSE_PATH Value: ~/.mcp-settings/jakarta-migration-license.json
    1. Save the configuration.
  4. Notes:
    1. If running local via the npm wrapper (npx @jakarta-migration/mcp-server) you generally do not need an API token.
    2. Use absolute paths for JAR or license locations.
    3. Restart your local MCP client after saving envs.

IMPORTANT: Distinguish the two places when you fill values in FastMCP — use the HTTP Headers section for the Authorization header (must be exactly "Bearer ") and the Environment Variables / ENVs section for any local configuration values (JAKARTA_MCP_JAR_PATH, license path, etc.).

Quick Start

View on GitHub Visit Website

More for Developer Tools

View All →

More for Coding

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.