abap-mcp

MCP server for SAP ABAP — offline static analysis, ABAP Cloud readiness, and RAP scaffolding. No SAP system. No credentials. Works on ABAP source wherever your AI agent works: a git checkout, an abapGit export, a code review, CI.

Built on abaplint (the open-source ABAP parser/linter) and the Model Context Protocol. TypeScript, 100% local — the server makes zero network calls and reads no user files: sources go in as text, findings come back as structured JSON. (The released-API list and abaplint's rule data are package-bundled assets that ship inside the install — no network, no user filesystem, at runtime.)

Why this exists

Every other ABAP MCP server is either a bridge to a live SAP system (ADT/RFC — needs credentials, a system, and trust) or a documentation search. But AI coding agents spend most of their time where the files are — editing abapGit repos, reviewing diffs, generating code — long before anything reaches a system. This server gives agents the missing feedback loop at that layer:

• "Does this ABAP parse? Is it clean? How does it perform?" → lint_abap (+ focus packs)

• "How far is this classic report from ABAP Cloud? Grade it." → check_cloud_readiness (A–D)

• "Did this rework make the code better or worse?" → compare_abap

• "Is MARA a released API? What do I use instead?" → check_released_api

• "Start me a correct RAP business object." → scaffold_rap_bo

• "What's in this 4,000-line class? Draw it." → get_abap_outline (+ Mermaid)

Related MCP server: ABAP-ADT-API MCP-Server

Quickstart

# Claude Code
claude mcp add abap-mcp -- npx -y abap-mcp

# or any MCP client (.mcp.json / mcp.json):
{
  "mcpServers": {
    "abap-mcp": { "command": "npx", "args": ["-y", "abap-mcp"] }
  }
}

From a clone instead:

npm install && npm run build
claude mcp add abap-mcp -- node /path/to/abap-mcp/dist/cli.js

Then ask your agent things like "lint this class against ABAP Cloud", "is zold_report cloud-ready?", or "scaffold a RAP BO for entity Booking on table zbooking, draft enabled".

CLI — same engine, no AI required

Every tool is also a subcommand, so it works in terminals and CI where no MCP client exists:

npx abap-mcp lint src/                          # lint files or whole directories
npx abap-mcp lint src/ --focus Performance      # themed pass: Performance | Security | Styleguide
npx abap-mcp lint src/ --rules-file org.json    # your org's abaplint rule pack, same engine
npx abap-mcp readiness src/ --fail-below 80     # repo-level ABAP Cloud readiness, scored + graded A–D
npx abap-mcp compare old/ new/                  # rework verdict: findings resolved/introduced, grade movement
npx abap-mcp scaffold --entity Travel --table ztravel --key travel_id --out ./out
npx abap-mcp outline src/zcl_monster.clas.abap  # navigate big objects (--mermaid for a diagram)
npx abap-mcp released MARA I_Product            # released-API status + CDS successor
npx abap-mcp explain exit_or_check              # rule rationale

Directories are walked recursively (abapGit naming), batched automatically, and readiness merges batches into one scored, categorized repo report. Exit codes are CI-friendly (1 on error findings / failed threshold).

Recipes, agents & CI

docs/COOKBOOK.md — practical recipes: the fix-until-clean loop, PR review without a transport, whole-repo migration triage, CI gates, per-persona use cases. examples/claude-code/ — drop-in agentic workflows: an abap-code-reviewer subagent, an abap-cloud-migrator sweep loop (readiness score as the loop condition), per-repo .mcp.json, and a GitHub Actions quality gate for abapGit repos.

Tools

Honesty box — what this is not

• Not ATC. The objective readiness score is still language-level: statements ABAP Cloud removed. Released-API coverage is now partial and offline: check_released_api and the releasedApiFindings in readiness reflect SAP's published Cloudification list as of the bundled snapshot date — they cover tables and function modules referenced in your source, not every API, and are only as current as the snapshot. A target system's own released-API list (ATC check API_RELEASE_STATE_CHECK / SAP_CP_READINESS) remains authoritative; treat an "absent from the list" result as "not released as of the snapshot", not as proof.

• Scaffold validation is tiered. Generated classes and CDS views are round-tripped through abaplint at Cloud level before they're returned (the generator and the linter share one parser). Behavior/service definitions are outside abaplint's checked surface — they are golden-tested canonical templates, and ADT activation is the final arbiter. Each generated file is labeled validated: "abaplint" | "template".

• Text-in only, by design. No user-filesystem walking, no network — the entire attack surface is a parser over strings you explicitly pass. (The released-API snapshot and abaplint's rule data are package-bundled assets imported from the install, not fetched or read from your disk.) For linting whole directories, use the abaplint CLI in CI, or the mcp-kit wrap-abaplint recipe this server grew out of.

Develop

npm install
npm run check     # typecheck + 149 tests + build — the CI gate
node dist/cli.js  # stdio MCP server
npx @modelcontextprotocol/inspector --cli node dist/cli.js --method tools/list

Tool descriptions are CI-graded (a rubric test enforces verb-first names, when-to-use, non-goals, described params, worked examples — the mcp-kit discipline; the full mcp-kit lint scores all nine tools 100/100).

Design

The decision log — why offline, why abaplint, why a dual-parse readiness diff, why the scaffolder validates its own output, what was deliberately left out — lives in docs/DESIGN.md.

Credits

• abaplint by Lars Hvam — the parser and rule engine underneath every tool here (MIT).

• SAP/abap-atc-cr-cv-s4hc — SAP's official ABAP Cloudification Repository (object release list), Apache-2.0. The bundled released-API snapshot (src/data/released-apis.json, snapshot 2026-06-10) is a compact transform of that data, redistributed under Apache-2.0 with attribution; see docs/DESIGN.md and scripts/build-released-api-index.mjs for the pipeline.

• mcp-kit — the production-MCP patterns this server follows (typed tool specs, transport discipline, description lint).

MIT © Akshay Palimkar. Not affiliated with or endorsed by SAP SE. "SAP", "ABAP" and "RAP" are trademarks of SAP SE; this is an independent open-source tool for developers working with them.