ARC-1
ARC-1 is a secure MCP server for AI-assisted SAP ABAP development, with read-first defaults and gated administrative or mutation workflows.
Read ABAP/CDS/DDIC source and metadata, including method bodies, diffs, revisions, inactive state, table previews, and SQL when explicitly enabled.
Search objects/source and navigate definitions, references, completions, hierarchies, relations, dependencies, CDS impact, where-used, and table structures.
Run ABAP lint/fix/format and SAP diagnostics such as syntax checks, ABAP Unit, ATC, dumps, traces, quickfixes, gateway errors, and authorization traces.
Inspect/manage SAP features, cache, packages, FLP catalogs/groups/tiles, API release states, CTS transports, and abapGit/gCTS repositories subject to safety gates.
Enforce enterprise controls: read-only default, explicit opt-ins for writes/data/SQL/transport/Git, package restrictions, multiple auth modes, rate limits, and audit logging.
Deployable as a Cloud Foundry app on SAP BTP with full platform integration including Destination Service, Cloud Connector, Principal Propagation, XSUAA OAuth proxy, and BTP Audit Log Service.
Available as a Docker image for containerized deployment, supporting various authentication methods and enterprise security configurations.
Connects AI assistants including GitHub Copilot to SAP systems via the ADT REST API, enabling AI-assisted SAP development with enterprise security controls and guardrails.
Supports OIDC/JWT authentication via Keycloak or any OpenID Connect provider for secure enterprise authentication to SAP systems.
Supports OIDC/JWT authentication via Entra ID, Keycloak, or any OpenID Connect provider for secure enterprise authentication to SAP systems.
Enterprise-ready MCP server for SAP ABAP systems connecting to SAP via the ADT REST API, providing 11 intent-based tools for reading/writing ABAP source, table data, CDS views, executing SQL, managing transports, and performing code analysis with enterprise security controls.
Uses SQLite for object caching in http-streamable deployments, enabling automatic source caching and dependency graph caching for improved performance.
ARC-1 — SAP ADT MCP Server
ARC-1 (pronounced arc one [ɑːrk wʌn]) — Enterprise-ready MCP server for SAP ABAP systems. Secure by default, deployable to BTP or on-premise, and hardened with large unit/integration/E2E test coverage.
ARC-1 connects AI assistants (Claude, GitHub Copilot, Copilot Studio, and any MCP client) to SAP systems via the ADT REST API. It ships as an npm package and Docker image.
Full Documentation | Quickstart | Security Review | Tool Reference | ARC-1 Updates | Blog Series
📬 Stay current with ARC-1 — get major releases, upgrade and security notes, practical guides, and occasional questions where your feedback can shape what comes next. Join ARC-1 Updates →
📖 New: AI ABAP Development blog series — long-form posts on AI for ABAP, ARC-1 design, and real-world BTP / Copilot Studio / Joule walkthroughs. Read the series →
Why ARC-1?
Built for organizations that need AI-assisted SAP development with guardrails. Inspired by the pioneering work of abap-adt-api, mcp-abap-adt, and vibing-steampunk — ARC-1 adds what's needed to run in production:
Security & Admin Controls
Safe by default — read-only, no free SQL, no table preview, no transport writes, no Git writes. Enable each capability with explicit
SAP_ALLOW_*flagsAction deny list — block specific tool actions with
SAP_DENY_ACTIONS(for exampleSAPWrite.delete), without exposing low-level operation codes to adminsPackage restrictions — limit AI write operations (create, update, delete) to specific packages with wildcards (
--allowed-packages "Z*,$TMP"). Read operations are not restricted by package — use SAP's native authorization for read-level access controlData access control (off by default) — table previews, saved SAPscript texts and SLG1 messages require
SAP_ALLOW_DATA_PREVIEW=true; freestyle SQL separately requiresSAP_ALLOW_FREE_SQL=true. Review enabled uses against the SAP API Policy, your SAP agreement, and internal data-governance rules.Experimental data-source emergency brake — approved data/SQL deployments can set
SAP_BLOCKED_DATA_SOURCES=USR02,PA0002. ARC-1 then parses each SQL request and resolves active CDS plus replacement-object lineage before execution, denying direct or transitive exact-name matches and failing closed when lineage is unsupported or cannot be proven. The empty default adds no metadata calls. This denylist is defense in depth, not a production allowlist or replacement for SAP authorization/CDS DCL; see Authorization & Roles.Transport safety — transport reads are available for review, while transport mutations require both
--allow-writesand--allow-transport-writes. Update/delete operations auto-use the lock correction number when no explicit transport is providedGit workflow safety — Git operations are disabled by default. Enable explicitly with
--allow-git-writes/SAP_ALLOW_GIT_WRITES=trueAPI-key profiles — multi-key HTTP deployments can assign
viewer,viewer-data,viewer-sql,developer,developer-data,developer-sql, oradminper keyWrites restricted to
$TMPwhen enabled — only local/throwaway objects; writing to transportable packages requires explicit--allowed-packagesHTTP security headers (helmet) on by default — HSTS, CSP, X-Frame-Options, CORP, X-Content-Type-Options. COOP is deliberately not set so popup-based OAuth flows (Copilot Studio) keep working. No flag to disable.
Opt-in CORS for browser MCP clients —
ARC1_ALLOWED_ORIGINS(comma-separated, exact match). Off by default; native MCP clients don't need itOpt-in client IP allowlist on SAP BTP Cloud Foundry —
ARC1_ALLOWED_CLIENT_IPSlets only listed addresses or CIDR ranges reach ARC-1, in front of authentication. Off by default; not suited to hosted clients such as Copilot Studio. Setup and limitsLayered rate limiting — three layers out of the box: per-IP OAuth and shared MCP HTTP edge limits (Layer 1; MCP inherits the historical derived cap unless
ARC1_MCP_HTTP_RATE_LIMIToverrides it), per-user MCP quota (Layer 2, off by default — multi-user deployments opt in viaARC1_RATE_LIMIT=60), and a server-wide SAP-bound semaphore (Layer 3, default 10, on). HonorsRetry-Afteron 429/503 from SAP / BTP gateways. See the Rate Limiting GuideDependency and release evidence — Dependabot, npm audit and Dependency Review checks, CodeQL, Trivy container scanning, npm provenance, and a best-effort CycloneDX SBOM for the release's production npm lockfile graph. Section 13 of the security guide lists what each artifact covers, how to verify it, and the gaps. Vulnerability response targets are best-effort and non-contractual.
Authentication
API key — simple Bearer token for internal deployments
OIDC / JWT — Entra ID, Keycloak, or any OpenID Connect provider
OAuth 2.0 — local browser-based login for BTP ABAP Environment service-key development
XSUAA — SAP BTP native auth with automatic token proxy for MCP clients
Per-user SAP identity — BTP Destination Service forwards the MCP user to SAP: Cloud Connector principal propagation for on-premise SAP, or
OAuth2UserTokenExchangefor BTP ABAP Environment
BTP Cloud Foundry Deployment
Deploy ARC-1 as a Cloud Foundry app on SAP BTP with full platform integration:
Destination Service — connect to SAP systems via managed destinations
Experimental multi-target mode — the default-off BTP mode discovers destinations marked
arc1.enabled=trueand exposes pinned SID/client plus read-only aggregate endpoints; scoped pinned PP writes require separate destination/IAM opt-ins (setup, administration)Optional target filtering — for shared multi-system gateways where teams need different target lists. Assign systems/clients through XSUAA roles; IAS changes are optional. This filters IAM-assigned targets, not automatically discovered SAP accounts.
Cloud Connector — reach on-premise systems through the connectivity proxy
Per-user destinations — user identity forwarded end-to-end via X.509 certificates for on-premise SAP, or exchanged for an ABAP bearer token for BTP ABAP Environment
XSUAA OAuth proxy — MCP clients authenticate via standard OAuth, ARC-1 handles the BTP token exchange
Audit logging — structured events to stderr, file, or BTP Audit Log Service
Token Efficiency
12 intent-based tools instead of 200+ individual tools — keeps tool selection simple, with the schema payload guarded by CI budgets and a hyperfocused 1-tool mode for tight context windows
Method-level read/edit — read or update a single class method, not the whole source (up to 20x fewer tokens)
Focused source and dependency context — use targeted
SAPReadfor exact implementation behavior. For business purpose, reviews or test design, start withSAPContext(action="deps", type=..., name=...)for available Knowledge Transfer Documents (SKTD/KTD) and dependency contracts, then compare requirements with source. Without documented requirements, intent is unverified.
Built-in Object Caching
Server-validated source caching — every SAP object read is cached in memory (stdio) or SQLite (http-streamable). Repeated reads use
If-None-Match/ETag conditional GET, so unchanged objects return from cache after SAP confirms304 Not Modified.Dependency parsing reuse — unchanged, authorized source can reuse parsed dependencies and contracts in memory. Aggregate dependency graphs are not cached; SAP authorization and source validation still apply.
KTD-aware context — Knowledge Transfer Documents use the source cache and are revalidated when composed into
SAPContext(action="deps").Live where-used —
SAPContext(action="usages")and CDS impact analysis query SAP's current repository index with the caller's identity; no startup repository scan is required.Active/inactive source views —
SAPReadacceptsversion="active" | "inactive" | "auto"and warns when the active source has an unactivated draft.Write invalidation — when
SAPWriteorSAPActivatemutates an object, both active and inactive source cache entries are dropped; next read revalidates or fetches fresh source.
See docs/caching.md for full documentation.
Testing
3,474 unit tests (
104unit test files, mocked HTTP)262-test default integration profile against live SAP systems, with explicit skip reasons when credentials or fixtures are missing
141-test default E2E profile that executes real MCP tool calls against a running ARC-1 server and live SAP system
Manual slow SAP profiles keep broad where-used, RAP full-stack, and recursive CTS release coverage out of the PR path (
test:integration:slow,test:e2e:slow, GitHub SAP Slow Tests workflow)CRUD lifecycle and BTP smoke lanes included (
test:integration:crud,test:integration:btp:smoke)CI matrix on Node
22and24; live SAP integration + E2E run on internal PRs and manual dispatch, with SAP jobs gated off for docs/chore PRs and external forksReliability telemetry + coverage published as informational CI signals (non-blocking)
Tools Refined for Real-World Usage
The 12 tools are designed from real LLM interaction feedback:
Tool | What it does |
SAPRead | Read exact ABAP source, method bodies, grep matches, table data, CDS views, access controls ( |
SAPSearch | Object search + full-text source code search across the system |
SAPWrite | Create/update/delete ABAP source and DDIC metadata with automatic lock/unlock (PROG, CLAS, INTF, FUNC, FUGR, INCL, DDLS, DCLS, DDLX, BDEF, SRVD, SRVB, SKTD/KTD, TABL, DOMA, DTEL, MSAG; availability adapts for BTP). Class updates can target local includes ( |
SAPActivate | Activate ABAP objects — single or batch (essential for RAP stacks), with guarded retry for the S/4HANA ED064 batch quirk. Publish/unpublish OData service bindings (SRVB) |
SAPNavigate | Go-to-definition, find references, code completion |
SAPQuery | Read saved SAPscript long texts or execute ABAP SQL; each path requires its own opt-in |
SAPTransport | CTS transport management (list/get/create/release/delete/reassign/release-recursive), transport layer/target lookup, package transport requirement checks, and reverse lookup history ( |
SAPGit | Git-based ABAP workflows across gCTS and abapGit (list/clone/pull/push/commit/branch/unlink) with backend auto-selection and safety gating ( |
SAPContext | Dependency APIs ( |
SAPLint | Local ABAP lint (system/release-aware presets, auto-fix, pre-write validation) + ADT PrettyPrint (server-side formatting) |
SAPDiagnose | Syntax check, ABAP Unit tests, ATC code quality, CDS test-case suggestions, active/inactive object-state comparison, generic ADT quickfix proposals/application deltas, gateway/system message diagnostics, short dumps, profiler traces, and the on-prem authorization trace ( |
SAPManage | Feature probing, cache statistics, package lifecycle/change-package operations, and FLP catalog/group/tile helpers |
Tool definitions automatically adapt to the target system (BTP vs on-premise), removing unavailable types and adjusting descriptions so the LLM never attempts unsupported operations.
Feature Detection
ARC-1 probes the SAP system at startup and adapts its behavior:
Detects HANA, gCTS, abapGit, RAP/CDS, UI5, and transport availability
Auto-detects BTP vs on-premise systems
Maps SAP_BASIS release to the correct ABAP language version
Each feature can be forced on/off or left on auto-detect
In shared-credential mode (technical user), runs a startup auth preflight once and blocks SAP tool calls with a clear error on 401/403 to avoid repeated failed logins and potential user lockout
Related MCP server: mcp-server-wazuh
ADT API Status and Strategy
For a custom MCP server such as ARC-1, SAP's Third-Party MCP Access reference architecture is the primary design and control baseline we recommend. For a shared service, start with BTP Cloud Foundry, XSUAA and strict principal propagation. SAP's API Policy FAQ Q56 allows custom MCP servers under conditions; Q32 confirms that Integration Suite is not mandatory.
SAP API Policy & Architecture Alignment explains that path, the controls ARC-1 already supports, and the remaining gaps. FAQ Q33 classifies ADT APIs as internal and limits them to endorsed development channels; ARC-1's direct TypeScript ADT client is not specifically identified as one. Clarify that channel and the intended AI-assisted development use with SAP before adoption, including dev/test. BTP hosting and security controls alone do not establish full policy adherence. Per-user SAP identity applies to PP; shared Basic modes retain a shared SAP identity.
Two ARC-1 capabilities can expose business data or execute ad-hoc SQL. Both are off by default and require explicit opt-in env vars, so the operator makes a deliberate decision before they are reachable:
Capability | Env var | Default | Policy note |
Table previews ( |
|
| Reads application data; authenticated callers also need |
Freestyle ABAP SQL ( |
|
| Executes ad-hoc ABAP SQL; authenticated callers also need |
Exact source blocklist (experimental) |
| empty (off) | Denies exact direct/transitive table or CDS dependencies; active mode is deliberately fail-closed and slower. |
When either capability is enabled, successful data-preview bodies are limited cumulatively per tool
call (2 MiB by default), and only two data-result calls per process remain admitted through parsing
and serialization. SAPQuery.maxRows is separately clamped to 10,000, but wide rows can reach the
byte limit much earlier. See Configuration before tuning
ARC1_MAX_DATAPREVIEW_RESPONSE_BYTES or ARC1_MAX_CONCURRENT_DATA_RESULTS.
With both flags at their defaults, ARC-1's data/sql rows are unreachable. FAQ Q33 excludes application-table reads, business-data export and backend SQL from ADT's intended development-tooling scope. Keep these flags off unless the specific use has a documented allowance or SAP authorization under the applicable agreements; internal approval or a technical opt-in alone is insufficient. Use Published business APIs for business-data integration.
ARC-1 combines capability discovery with conservative defaults and centralized authorization. Discovery establishes technical availability, not API-policy permission. Follow the reference architecture and verify both the API-specific allowance and the deployed controls.
Versioning & Stability
From 1.0 onward ARC-1 follows semantic versioning: patch releases fix bugs, minor releases add backward-compatible capability, and breaking changes to the MCP tool surface, configuration, or auth contract bump the major version.
Experimental, default-off features are excluded from this guarantee until they are promoted — they are clearly labeled and their surface may still change in a minor release. Today this covers the multi-target BTP mode (ADR-0006 / ADR-0007) and the data-source blocklist.
What changed per release: the annotated Release Notes give each release its impact and upgrade action; CHANGELOG.md lists every merged PR.
Quick Start
Install as an Agent Plugin — one portable install for the MCP server and all bundled SAP skills in GitHub Copilot, VS Code, Cursor, Codex, and other compatible clients:
copilot plugin marketplace add arc-mcp/arc-1
copilot plugin install arc-1@arc-1Agent Plugins 1.0 does not define secret prompts, so create the ARC-1 .env in the installed
plugin's persistent data directory before connecting to SAP. See the
Agent Plugin guide for client-specific installation,
safe configuration, and verification.
Install in Claude — pick your surface (full guide: Install in Claude):
Claude Desktop — download the latest
arc-1-*.mcpbfrom Releases and double-click it (or Settings → Extensions). Claude prompts for your SAP connection. (The.mcpbis attached to releases automatically; if the newest one doesn't have it yet, see Install in Claude.)Claude Code — one install for the MCP server and all SAP skills:
/plugin marketplace add arc-mcp/arc-1 /plugin install arc-1@arc-1Any MCP client / manual — run it directly:
npx arc-1@latest --url https://your-sap-host:44300 --user YOUR_USERTrying it out on your laptop? → Quickstart
Full local dev setup (Docker, cookie extractor, client configs)? → Local Development
Deploying for a team / BTP? → Deployment
Blog Series — AI ABAP Development
A long-form series on blog.zeis.de covering AI for ABAP development, ARC-1's design, and real-world walkthroughs:
Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP Development
ARC-1 on SAP BTP: Secure ABAP Agentic Development Beyond the Laptop
ARC-1 with Copilot Studio: SAP System Context Beyond Developers
ARC-1 with Joule Studio: Bringing Real ABAP System Context into Joule
Full list and new posts → blog.zeis.de/tags/ai-abap-development-series.
Documentation
Full documentation is available at docs.arc-1-mcp.com.
Guide | Description |
5-minute npx + Claude Desktop setup | |
Portable server + all skills for Copilot, VS Code, Cursor, Codex, and compatible clients | |
Desktop | |
Full local dev — all install methods, MCP client configs, SSO cookie extractor | |
Multi-user deployment — Docker, BTP Cloud Foundry, BTP ABAP | |
Choose the BTP topology and follow the correct deployment, auth, destination, and operations guides | |
MTA deployment, topology decision, role handoffs, and safe acceptance | |
Changes, roles, secrets, scaling, upgrades, rollback, and customer handover | |
BTP multi-target deployment, destinations, roles, and scoped pinned PP writes | |
Every flag and env var, one table | |
Update procedures per install method | |
Layer A / Layer B auth internals, coexistence matrix | |
Complete reference for all 12 tools | |
Add your own | |
System architecture with diagrams | |
Agent workflow patterns and best practices | |
Reusable ARC-1 agent skills, including GitHub Copilot in Eclipse and VS Code ADT setup | |
Long-form posts on AI for ABAP development, ARC-1 internals, and real-world walkthroughs |
Development
npm ci && npm run build && npm testSee CLAUDE.md for codebase structure, testing commands, and contribution guidelines.
Credits
Project | Author | Contribution |
oisee | Original Go MCP server — ARC-1's starting point | |
Marcello Urbani | TypeScript ADT library, definitive API reference | |
Mario Andreschak | First MCP server for ABAP ADT | |
Lars Hvam | ABAP parser/linter (used via @abaplint/core) |
License
MIT
Available Tools
9 toolsSAPContextARead-only
SHLP: default/deps returns active partial interface metadata, as SAPRead; no KTD or dependency traversal. Primary tool for understanding ABAP/CDS objects. KTD when available, then dependency contracts. Use SAPRead after SAPContext for exact source/methods/grep/drafts.
Decision rule — pick the action from the user's question:
"What breaks if I change ?" / "Who consumes <I_*>?" / "Blast radius" → action="impact" (DDLS only).
"Which includes/appends extend ?" → action="structure", type="TABL".
"What does do?" / "Explain" / "deps before editing" → action="deps" (default); type+name required.
"Find all callers of " → action="usages" (live SAP where-used lookup).
impact: upstream CDS dependencies, downstream where-used in RAP buckets, and sibling-consistency hints. Prefer it to SQL source scans. See action/options below. deps: target KTD when available + selected dependency contracts, derived from source (not SAP-native relationships or a complete inventory). Counts distinguish root candidates from recursive attempts. Standard helper names are filtered. For CDS, includes dependency DDL/field catalogs for cl_cds_test_environment. structure (TABL only): the DDIC include/append tree.
Inputs: name (required), type, depth, group, +8 more.
SAPDiagnoseA
ABAP diagnostics:
"syntax": check objects[] (CLAS/INTF/PROG/DDLS; version active/inactive). Single: prefer SAPRead SYNTAX.
"unittest": harmless ABAP Unit for CLAS/PROG/FUGR or DEVC (exact; includeSubpackages recurses).
"unittest_ci": harmless package tests with source reconciliation; empty/incomplete runs fail.
"atc": ATC (name+type/DEVC tree or objects [{type,name}], max 20). Omit variant for system default; unknown variant errors. "atc_variants": read variants/default, optional variant name filter.
"atc_ci": BTP-only package ATC CI; on-prem: atc type DEVC.
"cds_testcases": read suggested CDS Unit tests (name; SAP_BASIS 8.16+).
"object_state": active/inactive ETags/hashes/divergence (name+type; CLAS includes). No server-driven types.
"quickfix": proposals: name+type+source+line; optional column/sourceUri.
"apply_quickfix": text deltas, no save; quickfix inputs + proposalUri/proposalUserContent.
"dumps": ST22, newest: user/from/to/maxResults/filters; id=detail.
"feed_schema": optional dump filters; action only.
"traces": list profiler traces; id+analysis analyzes one.
"trace_start": arm NEXT matching execution (write; defaults HTTP, SQL on); reproduce, then read "traces".
"trace_requests": list armed traces. "trace_cancel": cancel by id (write).
"system_messages": list SM02 messages. "gateway_errors": list /IWFND/ERROR_LOG (on-prem; detailUrl or id+errorType for detail).
"odata_perf": read OData timing (url: host-relative; DB/ABAP/framework/auth); needs allowDataPreview.
"authorization_trace": read STUSERTRACE/SUAUTHVALTRC (on-prem; needs SAP_ALLOW_DATA_PREVIEW).
"cds_sql": read CDS native SQL (name).
"sql_trace_state" / "set_sql_trace_state" (sqlOn; needs SAP_ALLOW_WRITES) / "sql_trace_directory": ST05 SQL-trace control. Quickfix: syntax/ATC → quickfix → apply_quickfix → SAPWrite.
Inputs: action (required), id, to, url, +41 more.
SAPGitCDestructive
Git reads and gated abapGit workflows. gCTS mutations are quarantined. abapGit mutations need write/Git gates and allowedPackages ROOT/** or *; clone/pull evidence is unverified. external_info is gated HTTPS SAP egress.
Inputs: action (required), url, user, limit, +10 more.
SAPLintA
Run local abaplint rules on ABAP/CDS source (auto-selects cloud or on-prem rules by system type). Actions:
"lint": check source (errors+warnings) for ABAP (PROG/CLAS/INTF/FUNC) and CDS (DDLS).
"lint_and_fix": lint + auto-fix fixable issues (keyword case, obsolete statements); returns fixed source.
"list_rules": list rules + current config (no source).
"format": pretty-print via SAP's ADT formatter (needs source).
"get_formatter_settings" / "set_formatter_settings": read/update the system's global PrettyPrinter (indentation bool, style keywordUpper|keywordLower|keywordAuto|none; set is blocked read-only). lint/lint_and_fix/list_rules run locally; format/*_formatter_settings call SAP. Syntax: SAPRead(type="SYNTAX"); ATC/unit tests: SAPDiagnose.
Inputs: action (required), name, rules, style, +2 more.
SAPManageADestructive
Probe and report SAP system capabilities. Use BEFORE operations that depend on optional features (abapGit, RAP/CDS, AMDP, HANA, UI5/Fiori, CTS transports, FLP). Also handles package (DEVC) lifecycle.
Actions:
"features": cached feature status (fast, no round-trip; id, available, mode, probedAt). "probe": re-probe now (feature probes + auth + discovery refresh). "cache_stats": object cache health.
"create_package" / "delete_package" / "change_package": DEVC lifecycle via ADT packages API.
FLP read: flp_list_catalogs, flp_list_groups, flp_list_tiles (catalogId). FLP write: flp_create_catalog, flp_create_group, flp_create_tile, flp_add_tile_to_group, flp_delete_catalog. Classic designer tile/target-mapping model, deprecated since S/4HANA 2023; Work Zone exposure v2 needs LADIs (SAPRead type=UIAD).
"set_api_state": release/revoke an object's API release contract (objectUri, or name+objectType; apiState defaults RELEASED, contract defaults C1 — C0 for SRVD, C3 for classic views). Write counterpart of SAPRead(type="API_STATE").
Returns features + systemType ("onprem"/"btp"); "available: false" means do NOT attempt dependent operations.
Inputs: action (required), name, tile, title, +20 more.
SAPReadARead-only
Read SAP ABAP source/metadata. DDIC metadata: omit format. SHLP: active partial interface metadata; missing headers/assignments/appends are explicit. No drafts or source formats. For specs, reviews or pre-change context, prefer SAPContext first. TABLE_QUERY: filter with where, data preview required; CDS needs SAP_BASIS 752+. TABLE_CONTENTS: unfiltered preview. INACTIVE_OBJECTS: no name. TABL/DTT: technical settings. SYNTAX: read-only check (objectType+name, optional source). Global class declaration/implementation: MAIN (omit include). definitions/implementations contain local helpers.
Inputs: type (required), to, from, grep, +26 more.
SAPSearchARead-only
Search for ABAP objects, exact object-directory entries, or source code. Modes:
Object search (default): name pattern with wildcards (*); returns type, name, package, description, ADT URI.
TADIR lookup (searchType="tadir_lookup"): exact cross-package lookup of one or more names (prefer over long SAPQuery TADIR IN-lists).
Source code search (searchType="source_code"): full-text search across source (SAP_BASIS ≥ 7.51). Tips: BOR objects appear as SOBJ; the uri field feeds SAPNavigate, objectType feeds SAPRead/SAPWrite/SAPActivate. Searches object NAMES only — for field names use SAPRead(type='DDLS', include='elements') or SAPQuery on DD03L.
Inputs: names, query, source, maxResults, +4 more.
SAPTransportADestructive
Manage CTS transport requests (SE09/SE10). Actions: list (current user, modifiable), get (tasks + objects), create (always a Workbench (K) request — the package/target sets target & layer, not the request category; optional explicit target), release, delete, remove_object (keep the request), reassign (change owner), release_recursive (tasks then parent), check (does a package need a transport — type, name, package), history (legacy name: current object lock plus assignment candidates — type, name; not complete transport history; read-only, no write scope needed). IDs look like A4HK900123. Status: D/L=modifiable, O/P=releasing, R/N=released.
Inputs: action (required), id, name, type, +18 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Top-level domains are mostly distinct, but SAPRead, SAPSearch, SAPContext, and SAPNavigate all retrieve ABAP information and overlap on source lookup, where-used/references, and SHLP metadata. SAPRead SYNTAX also overlaps with SAPDiagnose syntax; the descriptions add routing guidance, but an agent can still hesitate between SAPContext usages, SAPNavigate references, and SAPSearch source_code.
All nine tools follow the same SAP + PascalCase convention (SAPRead, SAPSearch, SAPDiagnose, SAPLint, etc.) with no mixing of casing or separators. The pattern is predictable and maps clearly to broad domains, even if SAPManage is broader than its name suggests.
Nine tools is within the ideal 3-15 range and each maps to a recognizable SAP development category: read, search, diagnose, lint, transport, git, context, navigate, and manage. The count is not bloated, though several tools internally aggregate many actions.
There is no general SAPWrite or SAPActivate tool, even though SAPDiagnose's quickfix flow and SAPSearch tips explicitly route users to SAPWrite/SAPActivate, and apply_quickfix only returns unsaved text deltas. Core ABAP edit/create/activate lifecycle is therefore a dead end, despite strong read, diagnose, and transport coverage.
Maintenance
Related MCP Connectors
MCP server for Support & Service Management
MCP server for Product Management
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP Server for Nutanix Prism Central13MIT
- MIT
- AlicenseBqualityAmaintenanceABAP Development Tools MCP server with comprehensive tooling and documentation for SAP systems256738 npm106Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for SAP ABAP development that enables AI assistants and code editors to interact with SAP systems via ABAP Developer Toolkit (ADT) APIs, supporting read, create, update, and delete of ABAP objects.100MIT