sap-adt-mcp

MCP server and Python client for the SAP ADT (ABAP Development Tools) REST API. It gives your AI assistant the same operations that Eclipse ADT uses — searching the repository, reading and writing source code, activating, checking syntax, and working with transport requests — by talking to the same /sap/bc/adt/* endpoints.

Full technical documentation also in English: docs/PROJECT_DOCUMENTATION.md.

What you can do

• Search and browse — objects by wildcard (Z*, ZCL_*), package contents (including namespaces like /ACME/PKG), and metadata

• Read and write source — with locking, transport assignment, and activation in a single call; optionally saving/reading local files

• Activate and check syntax — with error messages by line and column

• Transports — list, create, release, and check whether an object needs one

• Create objects — programs, classes, interfaces, and packages (local or transportable)

• Export DDIC as Markdown — tables, data elements, domains, and views become readable context for the AI

• Work on older releases — media types are negotiated per endpoint and sap_system_info tells you what that system supports

Credentials are stored in the operating system credential manager; no password is ever written to a project file.

Related MCP server: mcp-abap-abap-adt-api

Requirements

SAP-side prerequisites (ICF services, roles, and authorization objects) are detailed in section 6 of the command reference.

Installation

Directly from GitHub (recommended)

pip install git+https://github.com/engoetz/sap-adt-mcp

This registers two commands on your PATH:

To run without permanently installing anything, using uv:

uvx --from git+https://github.com/engoetz/sap-adt-mcp sap-adt-mcp

From source code (for development)

git clone https://github.com/engoetz/sap-adt-mcp
cd sap-adt-mcp
python -m venv .venv && .venv/Scripts/activate   # Linux/macOS: source .venv/bin/activate
pip install -e ".[dev]"
python -m pytest tests -q

Setting up in the MCP client

After installation, the sap-adt-mcp command is already on the PATH — no absolute path needed:

{
  "mcpServers": {
    "sap-adt": {
      "command": "sap-adt-mcp",
      "args": []
    }
  }
}

Where to place this block:

If you prefer to run directly from source without installing the package, replace it with "command": "python", "args": ["/caminho/para/sap-adt-mcp/scripts/run_mcp.py"].

Verify

In Cursor, the server appears as user-sap-adt under Settings > MCP. To test in any client, call sap_list_environments() — it should return the list of saved connections.

Credentials

Via terminal (recommended)

sap-adt add DEV

The command asks for host, port, client, user, language, and HTTPS (Enter accepts the suggested value) and, finally, the password — entered twice, with no echo on screen. This way it doesn't end up in the shell history or the AI conversation history.

sap-adt list                      # conexões salvas e se têm senha
sap-adt edit DEV --port 8020      # alterar campos sem tocar na senha
sap-adt password DEV              # trocar apenas a senha
sap-adt test DEV                  # conectar e sondar os endpoints ADT
sap-adt delete DEV                # remover conexão e senha

There is no --password parameter: by design, the password is only entered via prompt. For automation, the SAP_PASSWORD environment variable is accepted.

The password goes to the OS keyring (Windows Credential Manager, macOS Keychain, Linux Secret Service). The other parameters are stored in ~/.sap-adt/environments.json, outside the project.

Via chat

sap_save_password(system_id="DEV", host="...", port=8000, client="100", user="username", password="...") does the same thing — but the password stays in the conversation log. Prefer the terminal.

First use

sap_connect(system_id="DEV")
sap_system_info()                       # o que este sistema suporta (rode em release antiga)

sap_search(query="Z*", object_type="CLAS")
sap_read_source(object_name="ZCL_MINHA_CLASSE", object_type="CLAS")

sap_write_source(
    object_name="ZCL_MINHA_CLASSE",
    object_type="CLAS",
    source_code="...",
    transport_request="DEVK900123"
)

Outside the MCP client, sap-adt test DEV performs the same diagnostics from the terminal.

Cross-release compatibility

Older systems (ECC, NetWeaver 7.3x) expose a subset of ADT and don't always understand the same media type versions. The client handles this on its own:

• Negotiated media types per endpoint, from newest to oldest, remembering what worked

• Discovery with fallbacks when /sap/bc/adt/discovery is not active in SICF

• Transport sent in both forms (corrNr in the query and sap-transportrequest header)

• sap_system_info probes the endpoints and tells you which tools won't work there

Details in section 6.7 of the reference.

MCP tools (25)

Connection and credentials

Repository

Source code

Transports

Creation and deletion

Parameters, examples, and return values for each one: docs/MCP_COMMAND_REFERENCE.md

Architecture

Cliente MCP  →  servidor MCP (stdio/JSON-RPC)  →  cliente REST ADT  →  SAP /sap/bc/adt/*

src/sap_adt/
├── client.py            # HTTP: autenticação, CSRF, sessões stateful, negociação de media type
├── credential_store.py  # ~/.sap-adt/environments.json + keyring do SO
├── repository.py        # pesquisa, navegação de pacotes, metadados
├── source.py            # leitura/escrita de fonte com bloqueio
├── activation.py        # ativação e verificação de sintaxe
├── transport.py         # transport requests (CTS)
├── ddic_export.py       # DDIC → Markdown
├── cli.py               # comando `sap-adt`
├── models.py            # dataclasses
├── exceptions.py        # hierarquia de exceções
└── mcp_server.py        # servidor MCP com as 25 ferramentas

Development

pip install -e ".[dev]"
python -m pytest tests -q

The tests are offline: no SAP system and no network are required. They cover URI resolution, the XML parsers fed with static responses (including the format from older releases), and the CLI. CI runs the suite on Linux and Windows, Python 3.10 and 3.13, and verifies that the package builds.

Contributions and bug reports are welcome via issues. When opening an issue, do not paste hostnames, usernames, clients, or proprietary code snippets — describe the behavior and, if possible, include the output of sap_system_info.

Documentation

License

Apache-2.0.

Independent project, with no affiliation, sponsorship, or endorsement from SAP SE. SAP, ABAP, and SAP NetWeaver are trademarks of SAP SE. The tool only consumes the publicly documented ADT API, using the user's own credentials.