Clément Ringot
Entries
LISA does the translation step only: it does not discover objects or manage transports, and its README pairs it with [an ADT MCP server](artifact:sap-adt-mcp-server) for those. Every write needs a transport request, and which object types it can write differs between public cloud or [the SAP BTP ABAP environment](artifact:btp-abap-environment) and on-premise or private cloud, and by release. Running it locally is meant for development and testing, not production.
MCP server for reading and writing ABAP object translations
It answers about the object catalogue, not about your code: nothing here reads your system, so it will tell you a table is not released and not that you used it. That check is ATC's, and this is what makes ATC's answer actionable.
MCP server answering whether SAP objects are released for ABAP Cloud
MCP server over the ADT REST API for ABAP objects
Writing and topics
IN TOPICS
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Details
History
- LISAEntered by intake from the README, found through ARC-1's extensions page, which names it in its example of driving a custom ABAP HTTP service.
- ROSACorrected against the README: 'The previously hosted public instance (on Railway) has been retired'.
- ROSATriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- First entry seenDiscovered via Added by hand, sap-ai-mcp-servers.
For your agent
- Ref
actor:clementringot- JSON
- /actors/clementringot.json
- MCP
- Connecting an agent