AI features

1. AI documentation of IFlows

Since 2605 Figaf Tool can generate AI documentation for IFlows. The documentation is a human-readable textual description of what an IFlow does, generated from its BPMN model by an LLM (OpenAI). It is stored per IFlow version, shown on the IFlow tracked object page, included in the generated XLSX documentation report, and used to build embeddings for Figaf AI Assistant.

The IFlow payload is sent to the configured LLM (OpenAI) for processing. Figaf Tool doesn’t send CpiExternalConfigurations, but some technical details (such as endpoints and system identifiers) may be included in the data sent to the LLM.

Follow steps to enable and use the feature:

  1. Configure OpenAI API Key on the Application configuration page.

  2. Enable Enable IFlow Documentation setting on the CPI agent configuration page. Optionally, restrict the scope with Documentation packages filter (regex) and Documentation IFlows filter (regex) settings.

    Since 2606, you can click Preview Matched Objects to check which packages and IFlows the configured filters match before generating documentation. The action validates the regular expressions (a clear error is shown for an invalid regex) and lists the matched objects. Save the agent before using the preview.

  3. Synchronize the agent.

    During synchronization Figaf Tool only creates documentation requests. The documentation and its embeddings are produced asynchronously by the Enable IFlow Documentation Scheduler and Enable IFlow Documentation Embedding Scheduler. So when synchronization is finished, it doesn’t mean that all documentation is generated yet.

2. Figaf AI assistant

Since 2605 Figaf Tool provides an AI assistant that lets you interact with the tool using natural language. You can use it, for example, to:

  • search IFlows by criteria (name, package, last change date, sender/receiver systems);

  • discover IFlow dependencies;

  • compare two IFlow versions.

The assistant is available in AI Assistant - open the AI Assistant chat in the Figaf Tool UI and type your request.

The AI Assistant is not available on the cloud version of Figaf Tool.

3. MCP server

Since 2606 Figaf Tool exposes an MCP (Model Context Protocol) server so its AI capabilities can be used from external AI clients (for example, Claude). The MCP server provides read-only tools to list agents, search IFlows, discover IFlow dependencies and list/compare IFlow versions.

The client connects to the MCP endpoint of Figaf Tool at https://<your-figaf-host>/api/mcp and authenticates using the OAuth 2.1 Authorization Code flow with PKCE. The login reuses the existing Figaf Tool authentication (local users and SAP BTP are supported in this release), so credentials are never shared with the AI client. The client is registered automatically during connection, so no OAuth client has to be created manually. Read the article to configure the MCP Connector for Claude.

To connect a client (for example, Claude):

  1. Add a new custom connector in the AI client and provide the Figaf Tool MCP URL https://<your-figaf-host>/api/mcp.

  2. Log in with your Figaf Tool user when prompted.

  3. The connection is approved automatically if your user has the IRTMcpReader (or IRTAdmin) role. Otherwise, the connection is refused.

The MCP server is available only for the on-premise (embedded) deployment. The Figaf Tool instance must be reachable from the internet and use a publicly trusted TLS certificate, so that the AI client can reach the /.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server, /connect/register, /oauth2/token and /api/mcp endpoints.

Access is read-only and requires the IRTMcpReader role (see Figaf Tool roles and permissions).