Figaf DevOps Suite
Ask your AI assistant about your iFlows, with real answers from Figaf
Connect Claude, ChatGPT or a self-hosted model to Figaf through its MCP server to find, compare and trace iFlows, check version history and see dependencies.
AI
MCP server
Your AI assistant knows nothing about your iFlows, so every question about your landscape starts with copying and pasting.
The Figaf MCP server lets an AI assistant work with the integration content Figaf already knows about. Integration developers and architects can connect Claude, ChatGPT or a self-hosted LLM to Figaf, and ask it to find iFlows, compare versions and show dependencies, instead of searching tenants by hand.
How it works
The Figaf MCP server is part of the Figaf tool and exposes these functions to the AI assistant:
- List agents, the systems Figaf is connected to
- Find iFlows in different ways, based on content in the iFlow, names or other criteria
- Check version history of an iFlow
- Compare versions
- Show iFlow dependencies
There is also a similar API, if you want to build your own tools on it.
The Figaf AI bot inside Figaf uses the same MCP server, but is easier to set up because it already has your context. To use the bot, you provide Figaf with your own OpenAI or SAP AI key. Data is sent directly to OpenAI on your key, not to Figaf, and only if you enable it.
Running on SAP BTP. When the MCP server was released in 2605, it was not yet supported for users of Figaf on SAP BTP. Since release 2606 the MCP server also works with a BTP user.
Business value
- Faster answers about the landscape. Finding an iFlow, checking what changed between versions, or seeing which flows depend on each other is a question to the assistant, not a manual search.
- Less dependence on individual specialists. Knowledge that used to sit with the developer who built a flow becomes something anyone on the team can ask about.
- Choose your own AI. You connect the assistant your organization already uses, including a self-hosted model, rather than being tied to one provider.
- Data stays under your control. The data goes directly to the AI provider on your own key. Figaf does not see it.
- Build on it. The same functions are available as an API for your own tools and agents.
Good to know
- The MCP server is part of the Figaf DevOps Suite. Available since release 2605, and for SAP BTP users since release 2606.
- Figaf plans to add more functions to the MCP server, to help you build integrations faster.
- Related features: AI search, Groovy editor with AI, automatic documentation.
Learn more
Included in
