Abapsmith - let your LLM work with ABAP code

[Artsemi]

Abapsmith - an ABAP MCP server built for traceability, with first-class support for ABAP frameworks like BOPF and RAP.

This MCP is based on ADT - the same protocol Eclipse uses. So it works with the system the way a developer does.

Why this one is worth a try

Safety - is the default. A single variable  ABAP_MODE controls what the assistant is allowed to do, and nothing else can lift that ceiling. It starts in "read". The "edit" mode unlocks write, activate, and run. The "admin" mode unlocks transport release and SAP standard objects. Data preview, dump variables, and driving transactions stay off in every mode until you name them explicitly - and data preview refuses to run on a productive system at all.

Every write can be undone. Before changing an object, the server records the previous source in a local journal. If the assistant writes something wrong, one call restores the exact prior version. If someone else changed the object in the meantime, undo detects the drift and refuses rather than overwriting their work.

The plugin includes Skills: how to build a RAP service in the right order, how to create DDIC objects with the right payload, how to get a transport number, how to recover from a bad write. The assistant reads these before it acts, instead of rediscovering ADT quirks on your system.

Easy to install. Add it as a Claude Code plugin in two commands, or clone and build for any other MCP client. Node 20 and an ADT-enabled system are the only requirements.

Getting started in five minutes

/plugin marketplace add Freight-Art/abapsmith
/plugin install abapsmith@abapsmith

Then a .env with your connection:

ABAP_URL=https://abap.example.com:44300
ABAP_USER=DEVELOPER
ABAP_PASSWORD=your-password
ABAP_CLIENT=001
ABAP_SID=A4H
ABAP_MODE=read

Start in read mode on a sandbox. Ask the assistant to explain a class, trace a where-used, or find out why a report dumps. When you're comfortable, switch to edit and let it write.

How does it work

Give the assistant a task like "add a validation to this RAP behavior and prove it works," and it can:

• Search for objects and read source, outlines, single methods, or DDIC definitions rendered as readable DDL.
• Create or change classes, programs, function modules, CDS views, behavior definitions, service bindings, tables, domains, and more.
• Activate the objects and read the syntax errors back.
• Run a class or a classic report and capture the output.
• Run ABAP Unit and ATC, then act on the findings.
• Set breakpoints, step through execution, and inspect any variable in scope.
• Read ST22 dumps when something goes wrong.
• Put the work on a transport request.

It covers the classic stack and the modern one: DDIC, function groups, dynpro screens, BOPF, enhancements and BAdIs, CDS, RAP, and OData services.

You can find full Capability matrix here - link

For contributors

The project is MIT licensed. Every capability in the documentation is backed by evidence from live tests, with a separate page listing what is unproven or not yet possible.

Repository: https://github.com/Freight-Art/abapsmith

Disclaimer:

This is a personal side project built in my own time. The views, code, and opinions expressed here are entirely my own and do not represent the official stance, roadmap, or support of SAP.