Raphael Ross (Progress Software) asked a question.

OpenEdge AI Assistant (fka MCP Connector) extended with all OpenEdge Knowledge Base articles

The OpenEdge AI Assistant (fka MCP Connector) has been extended with all OpenEdge KnowledgeBase articles (up to June 2026)! You only need to instruct your AI agent (e.g. CoPilot, Claude Code, Devin) to use it when needed. Could be a global/workspace rule or, even better, an agent skill. We will regularly upload the latest KB articles.

 

Example:

 

OpenEdge Knowledge Base

Use the OpenEdge AI Assistant (openedge-abl-mcp-server) and its KnowledgeBase collection for Progress Software knowledge base articles when:

  • Troubleshooting errors.
  • Diagnosing PAS for OpenEdge (PASOE), AppServer, or database startup issues.
  • Answering questions about known bugs, workarounds, or support resolutions.
  • How-to questions on OpenEdge features, APIs, or best practices.

 

Always query the KnowledgeBase collection before answering any question about error numbers, error messages, or operational problems.


  • Rob Fitzpatrick (White Star Software)

    When using the AI Assistant to reference KB material, can I assume it will be possible to reference the article meta-data as well as the content? E.g. environment info, article publication date, last modified date. Here is an example of "Environment" from an OE KB article:

     

    Environment

    Product: OpenEdge

    Version: 10.2B05 or later, 11.x

    OS: Windows 2008 R2

     

    https://community.progress.com/s/article/000039110

     

    Some examples/how-to in the documentation would be helpful for people getting up to speed on AI Assistant, e.g. best practices for crafting good prompts.

     

    And it might be worth reconsidering the terminology in the documentation, which describes it as the "OpenEdge AI Coding Assistant". This makes it sounds as if it would only be useful to ABL developers. The enhancement described above opens this tool up to many more roles in an OpenEdge shop: sys admin, support, QA, DBA, etc.

    • Roland de Pijper (Progress Software)

      Hi Rob,

      yes, all the meta data is stored in the AI Assistant's vector store.

       

      The documentation only describes the on-boarding and basic usage. However, we do have some more materials around it, e.g. https://www.progress.com/resources/videos/transforming-character-screens-into-rest-apis-with-openedge-ai-assistant.

      With the increased (but more realistic) AI costs, context engineering has become even more important then prompt engineering. We have a training/workshop (AI Accelerator) that focuses on these aspects.

       

      As far as I know, the documentation refers to the 'OpenEdge AI Assistant.' This is the official naming convention. If there are any specific pages or sections where you saw 'AI Coding Assistant,' could you point them out so we can get them corrected?

       

      Regards,

      Roland

      • Rob Fitzpatrick (White Star Software)

        AI Coding AssistantAI Coding AsstAI Coding Assistetc.

         

        Coveo search should find them all for you.

      • Roland de Pijper (Progress Software)

        Thanks Rob, will forward this to our doc team.

        The Coveo results all show the plugin that was created for PDSOE (the extra CHATGPT 'window'). That was/is called the AI Coding Assistant. Bit confusing...

        Didn't catch the others, maybe i should read our own documentation more often ;-)

  • Mike Fechner (Consultingwerk)

    Out of interest - is the K-Base integrated via A-RAG?

    • Roland de Pijper (Progress Software)

      Hi Mike,

      no, it's just another collection in the same vector store we use for the syntax.