SAP ABAP ADT MCP Server

MCP server for operating SAP ABAP Development Tools through ADT HTTP APIs.

Features

• Browser SSO assisted ADT login.
• ABAP repository search.
• Source and metadata read.
• Controlled create, update, activate, publish, and delete.
• ABAP Unit and ATC runs through ADT REST services.
• HTTP and STDIO transports.

Requirements

• Python 3.11+
• SAP ABAP system with ADT enabled
• Browser SSO access to the target system, or ADT-enabled Basic Auth credentials
• Optional communication arrangements for ABAP Unit (SAP_COM_0735) and ATC (SAP_COM_0901)

Install

python -m venv .venv
.\.venv\Scripts\pip install -e .
copy sap-mcp.example.yaml sap-mcp.yaml

Edit sap-mcp.yaml and set:

• abap_dev.system_url
• abap_dev.client, if the SAP system requires an explicit client such as 100
• abap_dev.auth_mode: sso, basic, or auto (default)
• abap_dev.username / abap_dev.password, if auth_mode is basic or auto
• allowed_packages
• allow_write / allow_activate
• Legacy communication_user / communication_password still work as aliases for Basic Auth credentials

Do not commit or share sap-mcp.yaml, .env, or .sap-mcp-session.json.

Start

HTTP:

$env:SAP_MCP_AUTH_TOKENS="dev-token"
uvicorn sap_mcp.server:app --host 127.0.0.1 --port 8000

STDIO:

python -m sap_mcp.stdio_server

HTTP endpoints:

• /mcp
• /healthz
• /logon/success

MCP Tools

• Login and connection: abap_adt_login, abap_adt_connect, abap_save_sso_session, abap_save_sso_cookie_header
• Read: abap_search_objects, abap_read_source, abap_get_object_metadata
• Write: abap_create_object, abap_update_source, abap_activate_object, abap_activate_objects, abap_delete_object, abap_publish_service_binding
• Quality: abap_run_unit_tests, abap_get_unit_test_run, abap_get_unit_test_result, abap_run_atc_checks, abap_get_atc_run, abap_get_atc_result
• ADT-compatible workflows: abap_list_destinations, abap_creation-*, abap_generators-*, abap_transport-*, abap_business_services-*

Supported Objects

• CLAS, INTF
• DDLS, DCLS, BDEF, DDLX, SRVD, SRVB
• TABL, DTEL, DOMA, DEVC
• PROG, FUGR, FUNC

For service bindings, abap_create_object accepts optional service_binding_version (V2 or V4, default V4). abap_publish_service_binding accepts optional odata_version (V2 or V4); when omitted, it tries to infer the version from SRVB metadata and falls back to V4 for existing callers.

Write, activate, publish, and delete operations are restricted by allowed_packages. Backend SAP authorizations still apply.

Login Flow

SSO mode:

1. Set abap_dev.auth_mode: "sso".
2. Call abap_adt_login.
3. Complete SAP SSO in the browser.
4. The callback stores the local ADT session.
5. Call abap_adt_connect.

Basic Auth mode:

1. Set abap_dev.auth_mode: "basic".
2. Set abap_dev.username and abap_dev.password.
3. Call abap_adt_connect.

Use read tools first; enable write and activation only when needed.