Claude Code for ABAP: Making Changes Through ADT, abapGit and MCP Servers

Keep this: job aid

Claude Code on ABAP: setup and change checklist

• Development only, an agent user (e.g. KENJI_AGT, role ZCMC_AGENT_DEV), never production; no CMQ/CMP destinations on the laptop.
• Route A: ADT MCP server in VS Code (port 2236) or Eclipse (2234), access restrictions on, edit tool off until needed. Route B: abapGit files, a person pulls.
• .mcp.json: server "adt", type http, header "Bearer ${ADT_MCP_TOKEN}"; verify with /mcp; never commit the token.
• Smoke test read-only: destinations, abap_read_file, ABAP Unit, ATC; it shows which tools work on your backend release.
• CLAUDE.md under 200 lines: @AGENTS.md, scope, naming, clean core (released APIs, stop rather than invent), definition of done.
• Manual pinned in managed settings (VS Code ignores project settings for the start mode); settings.json: defaultMode default, bypass disabled; deny exemptions, AI fixes, feeds, transport creation; ask for edits and pushes.
• Hooks: abaplint on abapGit files (exit 2 feeds back), Stop-hook evidence gate, audit line on mcp__adt__.*.
• Loop: read (plan mode) → plan with open questions → edit → activate → ABAP Unit → ATC → unified diff → PR with two approvals → a person releases.
• Prove tests by breaking the behavior; check every new SAP object exists and is released; never work around locks.
• API Policy 2.2.2 and FAQ Q33 per route: facts to counsel, counsel concludes; nothing is "approved by SAP".