ABAPilot brings SAP context into the AI coding tools your team uses. Its MCP connector connects supported clients to a licensed backend for SAP ECC and on-premise S/4HANA, enabling workflows such as explaining existing ABAP, reading dictionary definitions and validating proposed changes. This guide covers client setup and the controls to agree before a trial.
And because the assistant runs inside your editor, it also runs inside your process: the same skills, rules and instruction files your team already uses to govern AI-generated code apply to ABAP too. That second part is what this guide is about — because it’s the difference between “AI that writes ABAP” and “AI that writes your ABAP”.
Watch the four-minute ABAPilot demo or book a live ABAP workflow demo.
Connect ABAPilot to your AI coding client
ABAPilot by Crimson Consulting connects AI coding assistants to SAP ECC and on-premise S/4HANA. The MCP connector runs outside SAP; a licensed ABAP backend exposes the SAP operations. Installing the connector alone does not install that backend.
Before connecting, agree the backend version, enabled tools, SAP user, client and HTTPS endpoint with your SAP team. The machine running the connector needs Node.js/npm and network access to that endpoint. Start in an agreed development or sandbox system.
No ADT or Eclipse required. ABAPilot connects through its own ABAP backend and SICF service, rather than an ADT endpoint. Confirm backend compatibility with your SAP release before installation.
VS Code native MCP configuration
For VS Code’s native MCP integration, use .vscode/mcp.json with a servers object:
{
"servers": {
"abapilot": {
"type": "stdio",
"command": "npx",
"args": ["-y", "abapilot"],
"envFile": "${workspaceFolder}/.abapilot.env"
}
}
}Create the local .abapilot.env file with values supplied by your SAP team:
ABAPILOT_URL=https://<sap-host>:<https-port>/sap/bc/ZABAPilot
ABAPILOT_USER=<your-sap-user>
ABAPILOT_PASSWORD=<your-sap-password>
ABAPILOT_CLIENT=<sap-client>Add .abapilot.env to .gitignore before entering credentials. Restrict access to the file; it contains a plaintext password. Use your organization’s approved secret injection instead where available. Confirm the actual SICF path and trusted TLS certificate with your SAP team. See the VS Code MCP configuration reference.
Cursor, Claude Code and Codex use different configuration
- Cursor:
.cursor/mcp.jsonusesmcpServers; environment references use${env:NAME}. Follow the Cursor MCP instructions. - Claude Code: project configuration uses
.mcp.jsonwithmcpServers; environment references use${NAME}. Follow the Claude Code MCP instructions. - Codex: configure
[mcp_servers.abapilot]in~/.codex/config.toml, or a trusted project’s.codex/config.toml. Follow the Codex MCP instructions. This is separate from VS Code’s native MCP configuration.
Use the same connector command (npx -y abapilot) and ABAPILOT environment values with the syntax supported by your client. Ensure injected variables are available to the process that starts the connector. For repeatable team rollouts, pin a reviewed connector version and schedule updates. Client and backend versions determine the available tools.
Check the first connection
Start the server in your client’s MCP settings and inspect its tool list. Begin with a read-only request against an object approved for the trial: ask the assistant to explain an existing ABAP program and identify the SAP sources it used. Confirm the SAP identity and expected authorization failures before enabling writes. Review what SAP context your selected AI provider receives.
The public connector repository documents the connector and tool catalog. Backend capabilities, authorization checks and logging must be verified for the deployed version and endpoints.
The three layers that make generated code follow your standards
Getting AI-generated ABAP to compile is table stakes. Getting it to look like your team wrote it — your naming conventions, your error-handling pattern, your forbidden statements — takes three layers, and they stack:
Layer 1: IDE-side skills and rules
Put naming conventions, error handling and review requirements in the instruction files supported by your client. Version them with the repository and check that the assistant loads them. Instructions guide generation; they do not guarantee compliance or replace code review.
Layer 2: ABAPilot’s customer rule set
Agree the review and generation rules supported by your licensed backend version during setup. Keep a versioned rule pack and test it against examples that should pass and fail. Availability of a rule engine does not mean every connector operation invokes it.
Layer 3: The system as judge
Use system-side validation as a separate control. The public connector distinguishes sap_syntax_check, the validated sap_write_code_safe workflow and the low-level sap_write_code endpoint. A syntax gate is therefore not guaranteed for every write. Agree which endpoints are enabled, require review and testing, and verify the validation behavior on your deployed backend.
How to evaluate this with your team
Start with one existing custom program in an agreed development or sandbox system. Ask the assistant to explain its behavior, identify the dictionary objects it uses and draft documentation that a developer can check against the source.
Then choose a small change with clear acceptance criteria. Add your naming conventions and review requirements to the client instructions, inspect the proposed change, and run the agreed syntax checks and tests. Record the time spent on setup, correction and review as well as generation.
Compare the complete workflow with your normal process on comparable tasks. Use those observations to decide whether to expand a trial; a recorded demo alone does not establish customer productivity gains.
Watch a real session
Four minutes on a live SAP ECC 6.0 system: an AI agent reads the VBAK and VBAP structures from the data dictionary, creates a custom table, writes and activates an extractor program with an ABAP Unit test class, and runs the tests — all driven from VS Code through the ABAPilot MCP server. SAP GUI appears only at the end, to execute and confirm the result.
We also left in something most demos cut: a runtime error appears mid-session and the agent diagnoses and works around it. A demo where nothing ever breaks proves nothing.
The separate session replay below shows tool output from an ECC sandbox session on 24 August 2026. It is not a transcript of the video.
Why this beats a bundled chat window
The MCP approach brings SAP tools into your existing development workflow. Keep your prompts, repository instructions, code review and version history alongside the work. When changing clients or models, recheck configuration, tool availability, permissions and data handling.
FAQ
Does ABAPilot require ADT or Eclipse?
ABAPilot does not require ADT or Eclipse. Its local MCP connector connects over HTTPS to a licensed ABAP backend installed in SAP and exposed through an agreed SICF service. You need that backend, an authorized SAP user, network access and a compatible MCP client; installing the npm connector alone is not enough. Confirm release compatibility and enabled operations with your SAP team before a trial.
Which IDEs and AI clients work with ABAPilot?
ABAPilot uses an MCP stdio connector. VS Code, Cursor, Claude Code and Codex have different configuration formats. Confirm your client supports local stdio servers and validate the tool list with the deployed connector and backend versions.
Can the AI follow our internal ABAP naming conventions?
Yes. Put conventions in the instruction files supported by your client and agree any backend rule pack during setup. Check the generated result through review and tests; instructions alone do not guarantee compliance.
What stops non-compliant code from reaching the SAP system?
Use code review, tests, system-side syntax validation and restricted backend endpoints together. The public connector exposes both validated and low-level write tools, so a syntax check before every write must not be assumed.
Does each developer need their own SAP user?
For a developer trial, agree an individual SAP identity and the required permissions with your SAP team. Verify authorization failures and log attribution on the deployed endpoints before broadening access.
Should the MCP server run locally per developer or on a central server?
This guide covers a local stdio connector per developer. Central deployment requires a separate design for transport, authentication, identity propagation, secret storage and operations. Choose it based on those requirements rather than a fixed developer count.
See it running in your IDE
Book a 30-minute live demo → — bring your own VS Code, we bring the SAP system.