MCP serverMCP servertypeExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

ABAPilot

An MIT-licensed MCP connector for ECC and on-premise S/4HANA that reads ABAP source and dictionary context, whose SAP-side half is a licensed product you install in the system.

Reads ABAP source and dictionary context so an assistant can explain an existing program and support a change against what the system actually contains. The connector is free and open; what it talks to is not, and the README says so on the second line. The publisher also documents its own limits unusually plainly: operational checks across four installations in September 2026 covering dictionary reads, component reads, dispatcher-source reads and syntax checks — and stating that writes, activation, transports, authorisation boundaries and production readiness were not tested. A separate MIT ABAP REST framework is published for inspection, with the caveat that it is not proof the checked installations run that commit.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Agent access to your codeABAPAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.

Who is behind it

NicolasNicolasPersonMaintains this
In the atlas: maintains 1, contributes to 1
@NicoHern
maintainer

Before choosing this

Signals

CommercialCommercialIts maker offers it commercially

Its maker states it is offered commercially: “Connecting to SAP requires a licensed ABAPilot backend installed in your system.” (NicoHern/abapilot-mcp — README, checked 2026-10-22).

Conditions

PracticalFunctional boundary

The MIT licence covers the connector only: connecting to SAP needs a licensed ABAPilot backend installed in your system, so this is a commercial decision wearing an open-source badge on one half. Its own published checks did not cover writes, activation, transports or authorisation boundaries.

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your codeAn MCP server calls ADT or another SAP API of a running system for an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

An agent that plans and executes ADT calls is the case section 2.2.2 names. Check that the endpoints are published for the intended use, and that the design runs within a pathway SAP identifies for it.

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
MCP server
Origin
Independently maintained
Runtime
Node.js

As an MCP server

Runs as
local processinside the SAP system
Tools
49
Read-only
nostates it is not
Guardrails
5 quoted from README show all
  • the /ABAPILOT/CONFIG (or /TSRA/CONFIG) endpoint registry decides which endpoints are live

  • ABAPILOT_TOOLS narrows what a given MCP client sees

  • Pin a reviewed connector version for repeatable team rollouts.

  • safeguards are not implemented by the public Node connector and its input schema is incomplete

  • A syntax check must not be assumed for every write.

For agent access to your code

Read
sourcesearchwhere-usedDDICCDStable data
Change
writecreateactivatetransportsgit
Check
syntaxATCABAP Unit
Run
run codedumps
property statedstated nonot said

Connections3

Where ABAPilot runsOn-premiseBy its type: an MCP server is called by an MCP clientcallsdocumentedoutbounddocumentedoutboundYour MCP client, actorYour MCP clientSAP S/4HANA, SAP solutionSAP S/4HANASAP solutionABAPilot, moduleABAPilotSAP ERP (ECC), SAP solutionSAP ERP (ECC)SAP solution
SAPnot SAP's, or the project's ownstated in the documentdocumented only

README

quoted from NicoHern/abapilot-mcp under MIT, read
NicoHern/abapilot-mcp/README.mdOn GitHub

ABAPilot — MCP connector for ABAP development on SAP ECC and S/4HANA

Listed on mcpservers.org

ABAPilot by Crimson Consulting connects AI coding assistants to SAP ECC and on-premise S/4HANA. Use SAP source code and dictionary context to understand existing ABAP, review proposed changes and support development from your preferred MCP-capable coding client.

The connector is free and MIT-licensed. Connecting to SAP requires a licensed ABAPilot backend installed in your system.

Evidence you can inspect
  • Four-installation operational checks, 9 September 2026: two ECC and two S/4HANA installations passed dictionary reads, component reads, dispatcher-source reads and positive/negative syntax checks. This did not test writes, activation, transports, authorization boundaries or production readiness.
  • Public MIT-licensed ABAP REST framework: inspect the table-driven endpoint registry, dispatcher and example handlers. This framework is separate from the licensed ABAPilot backend and is not proof that the checked installations run an identical public commit.
  • Published MCP catalog: the npm 1.0.6 connector exposes 49 tools. Catalog discovery is not evidence that every operation works on a particular SAP installation.
Start with an existing ABAP program

Ask your assistant to explain a program using source and dictionary definitions retrieved from SAP. Review the references it used before moving to a proposed change. Available operations depend on the connector version, installed backend and enabled endpoints.

Architecture and prerequisites

The MCP connector runs outside SAP and calls the licensed SAP-side backend. Agree the SAP release, backend version, HTTPS endpoint, individual user permissions and permitted operations with your SAP team before a customer trial.

Start the connector using npx -y abapilot. This command does not install the SAP backend. Follow the linked setup guide for client-specific configuration and secret handling. Pin a reviewed connector version for repeatable team rollouts.

Technical reference: Architecture

Tools

The current repository catalog lists 49 tools. Availability depends on the installed connector, backend version and enabled endpoints.

Business data

  • sap_read_table_data — Reads actual data from a SAP table with optional WHERE clause filtering and metadata inclusion
  • sap_read_table_data_enhanced — Query data from a SAP table with optional WHERE clause filtering
  • sap_read_table_paginated — Read table data with pagination support for large result sets
  • sap_stream_table_data — Streams large table data using offset-based pagination
  • sap_smart_table_query — Execute a table query with automatic metadata-driven enhancements
  • sap_multi_table_query — Execute a multi-table query with proper joins and optional aggregation
  • sap_count_rows — Estimate row count for a table BEFORE fetching data
  • sap_analyze_query — Analyze a natural language query and return intelligent guidance for building the SAP query
  • sap_search_tables — Search the Data Dictionary for tables matching a keyword

Data Dictionary & metadata

  • sap_read_table_structure — Retrieves the metadata of a Data Dictionary table including field definitions, data types, keys, and descriptions
  • sap_read_object_details — Read comprehensive details about any SAP repository or DDIC object
  • sap_read_object_info — Get metadata about an ABAP object including creation date, last changed date, author, and package
  • sap_check_type_exists — Checks whether a type exists in the SAP Data Dictionary and returns its kind
  • sap_read_domain_values — Retrieves the fixed values defined for a domain
  • sap_read_field_domain_values — Get domain fixed values for a specific table field
  • sap_read_foreign_keys — Read foreign key relationships for a table from Data Dictionary (DD08L)
  • sap_infer_joins — Automatically detect join keys between two tables based on domain matching
  • sap_get_field_metadata — Get enriched metadata for SAP table fields with semantic classification
  • sap_list_package_objects — List all ABAP repository objects in a development package (DEVCLASS)

ABAP code

  • sap_read_code — Retrieves the source code of an ABAP object (program, class, or function group)
  • sap_read_includes — Retrieves all include files for a program with their source code
  • sap_read_dynpros — Retrieves screen definitions for a program including field lists
  • sap_read_texts — Retrieves text elements (selection texts, text symbols) for a program
  • sap_read_where_used — Queries SAP's cross-reference tables (WBCROSSGT/WBCROSSI) to find what objects use a given object (forward) or what a given object uses (inverse)
  • sap_get_enhancements — List ALL enhancements for a SAP transaction or program in one call
  • sap_syntax_check — Validates ABAP source code for syntax errors without creating or activating it
  • sap_write_code — Forward a source-write request; object support, validation and activation depend on the installed backend
  • sap_write_code_safe — Forward a request to the backend; safeguards are not implemented by the public Node connector and its input schema is incomplete
  • sap_patch_code — Forward a source-patching request; supported patch arguments and validation depend on the backend

Operations & troubleshooting

  • sap_read_dumps — Query ABAP runtime errors (short dumps) from SAP's ST22 transaction
  • sap_read_dump_details — Get detailed information for a specific short dump including full error texts, cause, and solution
  • sap_read_syslog — Query system log entries from SAP's SM21 transaction
  • sap_read_jobs — Query background job information from SAP's SM37 transaction
  • sap_run_program — Request report execution; output depends on the backend, with no timeout or background-job fallback implemented by this connector
  • sap_run_transaction — Run the ABAP report behind a report transaction code, optionally with a selection-screen variant, and return its list output
  • sap_save_variant — Create or overwrite an ABAP selection-screen VARIANT for a report, so it can be reused by sap_run_program (and the performance trace / headless…
  • sap_read_user_locks — Query user lock status from USR02 table
  • sap_diagnose_message — Diagnose a SAP error/warning/info message end-to-end
  • sap_lookup_t100 — Look up a specific SAP T100 message by message class and number
  • sap_lookup_error — Analyze a SAP error message using all available external knowledge sources

Audit & compliance

  • sap_read_change_docs — Query change documents from CDHDR/CDPOS tables
  • sap_read_change_docs_v2 — Optimized change document query using function modules
  • sap_discover_change_object — Find the change document OBJECTCLAS for a table by querying TCDOB
  • sap_scan_security_notes — Discover ABAP Security/HotNews notes for a SAP patch-day month and rank them by relevancy to this system
  • sap_check_notes_relevancy — Check relevancy of one or more SAP Note numbers against this system (component/SP levels, download state, implementation readiness)

Translation

  • sap_read_translations — Reads translatable texts from a SAP object in source and optionally target language
  • sap_write_translations — Writes translated texts back to a SAP object
  • sap_translate — Composite tool: reads translatable texts from a SAP object, translates them using AI, and optionally writes them back

Knowledge

  • sap_search_knowledge — Search SAP documentation and community for information on any SAP topic

The catalog is gated in two places. In your system, the /ABAPILOT/CONFIG (or /TSRA/CONFIG) endpoint registry decides which endpoints are live — switch one off and the tool stops working, with no client change. On the client side, ABAPILOT_TOOLS narrows what a given MCP client sees:

"env": { "ABAPILOT_TOOLS": "sap_read_table_data,sap_read_code,sap_syntax_check" }

The licensed backend may expose operations beyond this public catalog. Agree the required capabilities and verify them on the deployed version before a trial.

Validation and data handling

The public connector advertises source and dictionary readers, syntax checking and write endpoints. Validation and deployment safeguards depend on the installed backend. A syntax check must not be assumed for every write. Confirm the enabled endpoints, validation behavior, authorization failures and log attribution on your deployed version.

Review which SAP context your chosen AI client and model provider receive. Using your own API key does not by itself establish local processing or a particular retention policy.

Evaluate the workflow

The September 2026 walkthrough uses Claude Code, ABAPilot and a lifecycle skill to change a sandbox copy of an existing material-description report, then update its technical specification and test scenarios. Length and invalid-character checks run independently; a regex-cache regression checks that changing patterns does not reuse a stale expression.

The final recorded ABAP Unit run passed 14 test methods. The scenario document records 15 passes out of 16 scenarios: 14 unit scenarios and a documentation review, with manual report integration not run. Material selection, SALV rendering, MM03 navigation and runtime termination before data selection were not verified by the unit run. The original report and material-master data were not changed. This is one configured sandbox installation, not evidence of production readiness or a promise of identical support on every SAP release.

The technical case contains screenshots and the coverage boundaries. The earlier four-minute creation demo is also available.

The recorded demo shows one sandbox workflow. In a live demo we can discuss your system, IDE and requirements before agreeing a customer trial. Choose a time.

Further reading

MIT, read
Agent access to your code
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loopfrom ABAP
  2. arc-1-bopf-enharc-1 extension for reading and maintaining BOPF enhancementsfrom ABAP
  3. HammerNative macOS code editor for ABAP and CDSfrom ABAP
  4. arc-1-lspEdition of ARC-1 that runs ADT calls through adt-lsfrom ABAP
  5. arc-1MCP server over the ADT REST API for ABAP objectsfrom ABAP
  6. arc1-abap-bridgeVS Code bridge between arc-1 and ADT for VS Codefrom ABAP
  7. arc1-adt-abap-mcp-extEclipse add-on enabling the ADT MCP server with read-only toolsfrom ABAP
  8. capforgeMCP server scaffolding CAP and CDS checked by cds compilefrom CAP
  9. ABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kirofrom ABAP
  10. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  11. @mcp-abap-adt/coreABAP ADT MCP server published as an npm scope and pluginfrom ABAP
  12. @cap-js/mcp-serverMCP server for CAP development: model and docs searchfrom CAP
  13. chandrashekhar-mahajan/abap-mcp-serverABAP MCP server with ADT tools and five authentication strategiesfrom ABAP
  14. dassian-adtFork of mcp-abap-abap-adt-api with 25 tools and session recoveryfrom ABAP
  15. erpl-adtC++ binary speaking the ADT REST API as a CLI and MCP serverfrom ABAP
  16. bw-modeling-mcpMCP server for BW/4HANA modelling objectsfrom BTP/BAIP
  17. EPOD ADT MCP ServerMCP server for ABAP on the ADT session, in Eclipse or standalonefrom ABAP
  18. ZARC1_EXTENSION_FORMSarc-1 extension for SAPscript and Smart Forms objectsfrom ABAP
  19. fgalastri/MCP_ABAPValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.from ABAP
  20. fr0ster/mcp-abap-adtABAP MCP server with full CRUD on on-premise and ABAP Cloudfrom ABAP
  21. abapsmithABAP MCP server over ADT with a local journal that can undo writesfrom ABAP
  22. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP systemfrom ABAP
  23. aibap.mcpGo MCP server that writes, activates and runs ABAP classes via ADTfrom ABAP
  24. BellaEclipse plugin bringing Claude into ABAP Development Toolsfrom ABAP
  25. Maherd18/sap-mcp-serverPolicy-checked MCP server for ABAP development over ADTfrom ABAP
  26. sapdumpmcpMCP server reading ABAP short dumps over ADTfrom ABAP
  27. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  28. mcp-abap-abap-adt-apiWrite-oriented MCP server over abap-adt-apifrom ABAP
  29. mcp-abap-adtRead-oriented MCP server fetching ABAP programs, classes, tablesfrom ABAP
  30. SAP MCP Connection ManagerWindows desktop manager handing SAP connections to assistants over MCPfrom ABAP
  31. vibing-steampunkADT-to-MCP bridge in Go reaching past what ADT exposesfrom ABAP
  32. ADT MCP ServerLocal HTTP MCP server started from ABAP Development Tools for VS Codefrom ABAP
  33. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsfrom ABAP
  34. SAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Codefrom ABAP
  35. @sap/mdk-mcp-serverMCP server with five tools for Mobile Development Kit workfrom BTP/BAIP
  36. @sap-ux/fiori-mcp-serverMCP server for creating and editing Fiori applicationsfrom UI5
  37. ABAPDocMCPMCP server turning a transport request into a WRICEF specificationfrom ABAP
  38. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1from ABAP
  39. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP toolsfrom ABAP
  40. @ui5/mcp-serverMCP server for UI5 development with ten toolsfrom UI5
  41. abap-adt-cliCLI that pulls and pushes ABAP packages as local files over ADTfrom ABAP
  42. workskong/mcp-abap-adtLight MCP adapter for ABAP over ADT, documented in Koreanfrom ABAP
  43. KlystronMCP server in ABAP inside the application server, with agent skillsfrom ABAP
  44. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlistfrom ABAP
  45. ABAP-AI-CODE-TOOLSabapGit package adding create, modify and delete tools to ABAP AI Codefrom ABAP
  46. ABAP AI CodeAgentic coding assistant in ABAP that runs as an SAP GUI reportfrom ABAP
  47. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI toolsfrom ABAP

Details

Sources3
sap-ai-mcp-serversdiscovered herechecked
github.com/NicoHern/abapilot-mcptree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
discovered viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Flavors1
Standard ABAP
“ABAPilot by Crimson Consulting connects AI coding assistants to SAP ECC and on-premise S/4HANA.” — NicoHern/abapilot-mcp — READMEchecked
History in the atlas2
  1. Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
  2. First seen.
For your agent
Ref
artifact:nicohern-abapilot-mcp
JSON
/artifacts/nicohern-abapilot-mcp.json
MCP
Connecting an agent