Server data from the Official MCP Registry
Offline SAP ABAP static analysis, Clean Core readiness checks, and RAP scaffolding. No SAP system.
Offline SAP ABAP static analysis, Clean Core readiness checks, and RAP scaffolding. No SAP system.
The abap-mcp server is a well-designed, security-conscious tool for offline ABAP static analysis. It explicitly avoids network calls and filesystem access at the MCP layer, has no authentication requirements (appropriate for a local analysis tool), and properly handles user-supplied ABAP source text. Minor code quality observations exist around error handling breadth and input validation edge cases, but the architecture and implementation are fundamentally sound. Permissions are appropriate for the stated purpose. Supply chain analysis found 2 known vulnerabilities in dependencies (2 critical, 0 high severity). Package verification found 1 issue.
4 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-palimkarakshay-abap-mcp": {
"args": [
"-y",
"abap-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.)
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:
lint_abapcheck_cloud_readinesscheck_released_apiscaffold_rap_boget_abap_outline# 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".
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 readiness src/ --fail-below 80 # repo-level ABAP Cloud readiness, CI-gateable
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
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).
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.
| Tool | What it does |
|---|---|
lint_abap | abaplint static analysis over ABAP/CDS/BDEF sources → structured findings with rule docs links. Presets: style (default, snippet-friendly), full, syntax-only; per-rule overrides. |
check_cloud_readiness | Dual-parse diff (classic baseline vs Cloud): statements that are valid today but illegal in ABAP Cloud become categorized blockers (dynpro, list output, native SQL, …) with a transparent score; code broken at the baseline is reported separately, not counted as migration work. Now also surfaces a separate, dated released-API cross-check (releasedApiFindings): direct access to non-released classic tables and deprecated-API usage found in the source, with CDS successor hints — informational, not folded into the score. |
check_released_api | Looks up objects (tables, CDS views, function modules, classes, …) in SAP's bundled Cloudification snapshot → released / deprecated / not-released per object, plus a curated CDS successor for common classic tables. The released-API half of readiness, offline. |
scaffold_rap_bo | Generates the canonical RAP managed-BO stack (root view, behavior definition strict(2) + optional draft, behavior class + handler locals, projection, metadata extension, OData V4 service definition) plus suggested table DDL, activation order and next steps. |
list_abap_rules | Browse abaplint's ~180 rules (filter by text or tag). |
explain_abap_rule | One rule in depth — rationale (often Clean ABAP), examples, docs URL. |
format_abap | Offline pretty-printer (keyword case + indentation). |
get_abap_outline | Classes/methods/visibility/interfaces/FORMs of a source — navigate big objects without reading them whole. |
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.validated: "abaplint" | "template".wrap-abaplint recipe this server grew out of.npm install
npm run check # typecheck + 122 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 eight tools 100/100).
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.
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.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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.