Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-6624

Developer Lightspeed integration layer

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Application Analysis, Kai
    • None
    • Developer Lightspeed for MTA integration layer
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do

      Epic Goal

      Provide an integration layer that allows the capabilities of MTA and Developer Lightspeed for MTA to be integrated with other agents.

      Why is this important?

      Developer Lightspeed for MTA is only available within our own IDE extension, and limited to the user experience we built around it. While this is still a valid scenario for large Enterprise environments that want to have a tight control over how Third Party developers execute modernization at scale, it falls short for advanced developers that use coding assistants like Claude, Cursor or Copilot.

      Our intention is exposing the migration capabilities of MTA and Developer Lightspeed for MTA for them to be leveraged by standard coding agents and assistants, ensuring advanced architects and Third Party factory developers get consistent results when they attempt modernization of their applications, ensuring everything stays aligned with corporate standards.

      Scenarios

      • Integration with coding assistants and agents via MCP server and/or an standalone agent.
      • Internal usage in the Hub to automate fixes at repository level (batch remediation) without the need of using the IDE extension.

              pgaikwad1@redhat.com Pranav Gaikwad
              rromanni@redhat.com Ramon Roman Nissen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: