ABAP Accelerator

io.github.openkashPublished by GitHub account openkashv1.0.1Updated Oct 24, 2026

MCP server for SAP ABAP development with 15 tools for ABAP objects, syntax, ATC, and more

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Local MCP server that connects an assistant to a SAP system's ADT API so it can browse, edit, check and activate ABAP development objects.

What you can do
  • Check the SAP connection status and list ABAP objects in a package
  • Search for ABAP objects and read their source code
  • Create objects, update source code, check syntax, and activate single objects or batches
  • Run ATC quality checks, execute unit tests, and list or create/update test classes
  • Retrieve migration analysis and transport requests
When to use it
Useful for ABAP developers who want an AI assistant to work directly inside a SAP development, sandbox, QA or test system: reading and editing source, running syntax checks, ATC checks and unit tests, and managing transports.
Requirements
Runs locally over stdio from the PyPI package abap-accelerator (for example via uvx or pip install). Needs network access to the SAP system and the required environment variables SAP_HOST, SAP_INSTANCE_NUMBER, SAP_CLIENT, SAP_USERNAME and SAP_PASSWORD; optional ones include SAP_LANGUAGE, SAP_SECURE, SSL_VERIFY, CUSTOM_CA_CERT_PATH and LOG_LEVEL. Values can also come from a .env file.
Before you install
Requires SAP credentials (SAP_USERNAME, SAP_PASSWORD) stored in the client config or a .env file. It can create and change ABAP objects, update source, activate objects and create or update test classes, so changes land in the connected SAP system; the README advises using it only in non-production systems. Disabling SSL_VERIFY weakens connection security and is described as for testing only.

Installation

In SourceWeft

  1. Open ABAP Accelerator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ABAP Accelerator MCP Server

SAP ADT API Model Context Protocol (MCP) server for ABAP development. Works with any MCP-compatible client including Claude Code, Amazon Q Developer, Kiro, Cursor, Windsurf, and more.

Fork notice: This is a fork of AWS ABAP Accelerator for Amazon Q Developer, repackaged for PyPI and optimized for local stdio runs. The original project targets Docker/ECS enterprise deployments; this fork focuses on the simplest path: pip install and go.

Quick Start

bash
pip install abap-accelerator

Create a .env file or set environment variables:

bash
SAP_HOST=your-sap-host.example.com   # or host:port (e.g., 10.0.0.1:44300)SAP_INSTANCE_NUMBER=00                # used to calculate port when SAP_HOST has no portSAP_CLIENT=100SAP_USERNAME=your_usernameSAP_PASSWORD=your_password

Run:

bash
abap-accelerator

That's it. The server starts in stdio mode and is ready for your MCP client.

MCP Client Configuration

Add to your client's MCP config file:

Claude Code (.mcp.json in project root):

json
{  "mcpServers": {    "abap-accelerator": {      "command": "abap-accelerator",      "env": {        "SAP_HOST": "your-sap-host.example.com",        "SAP_INSTANCE_NUMBER": "00",        "SAP_CLIENT": "100",        "SAP_USERNAME": "your_username",        "SAP_PASSWORD": "your_password"      }    }  }}

Amazon Q Developer (~/.aws/amazonq/mcp.json or workspace .amazonq/mcp.json):

json
{  "mcpServers": {    "abap-accelerator": {      "command": "abap-accelerator",      "env": {        "SAP_HOST": "your-sap-host.example.com",        "SAP_INSTANCE_NUMBER": "00",        "SAP_CLIENT": "100",        "SAP_USERNAME": "your_username",        "SAP_PASSWORD": "your_password"      }    }  }}

Kiro (.kiro/settings/mcp.json):

json
{  "mcpServers": {    "abap-accelerator": {      "command": "abap-accelerator",      "env": {        "SAP_HOST": "your-sap-host.example.com",        "SAP_INSTANCE_NUMBER": "00",        "SAP_CLIENT": "100",        "SAP_USERNAME": "your_username",        "SAP_PASSWORD": "your_password"      }    }  }}

Tip: If you run abap-accelerator from a directory with a .env file, you can omit the env block — the server loads .env automatically.

Environment Variables

VariableRequiredDefaultDescription
SAP_HOSTYes-SAP hostname or host:port
SAP_INSTANCE_NUMBERYes-Instance number (00-99), used to calculate port
SAP_CLIENTYes-SAP client number (e.g., 100)
SAP_USERNAMEYes-SAP username
SAP_PASSWORDYes-SAP password
SAP_LANGUAGENoENSAP language
SAP_SECURENotrueUse HTTPS
SSL_VERIFYNotrueVerify SSL certificates (set false for self-signed)
CUSTOM_CA_CERT_PATHNo-Path to custom CA certificate
LOG_LEVELNoINFOLogging level (DEBUG, INFO, WARNING, ERROR)

SAP Port Calculation

The server calculates the SAP port from the instance number:

Instance NumberHTTPS PortHTTP Port
00443008000
01443018001
02443028002

Formula: HTTPS = 44300 + instance_number, HTTP = 8000 + instance_number

If SAP_HOST includes a port (e.g., 10.0.0.1:44300), the instance number is ignored.

Available Tools

ToolDescription
aws_abap_cb_connection_statusCheck SAP connection status
aws_abap_cb_get_objectsList ABAP objects in a package
aws_abap_cb_get_sourceGet source code of an object
aws_abap_cb_search_objectSearch for ABAP objects
aws_abap_cb_create_objectCreate new ABAP object
aws_abap_cb_update_sourceUpdate source code
aws_abap_cb_check_syntaxCheck syntax of source code
aws_abap_cb_activate_objectActivate ABAP object
aws_abap_cb_activate_objects_batchBatch activate objects
aws_abap_cb_run_atc_checkRun ATC quality checks
aws_abap_cb_run_unit_testsExecute unit tests
aws_abap_cb_get_test_classesGet test classes for an object
aws_abap_cb_create_or_update_test_classCreate/update test class
aws_abap_cb_get_migration_analysisGet migration analysis
aws_abap_cb_get_transport_requestsGet transport requests

Environment Guidance

This tool provides direct access to ABAP development objects. Use it in non-production environments:

IntendedNot Recommended
Development (DEV)Production (PRD)
Sandbox (SBX)Pre-production
Quality Assurance (QAS)
Test / Training / Demo

Troubleshooting

SSL Certificate Errors (SSL: CERTIFICATE_VERIFY_FAILED):

  • Set CUSTOM_CA_CERT_PATH to your corporate CA cert
  • For testing only: set SSL_VERIFY=false

Connection Timeout:

  • Verify SAP system is reachable from your network
  • Check firewall allows port 44300 (or your SAP port)
  • Verify SAP ADT services are enabled (transaction SICF)

Debug Logging:

  • Set LOG_LEVEL=DEBUG for verbose output

License

MIT No Attribution (MIT-0) — see LICENSE

Original work Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.

Source: README.md at commit f5e457e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts