Read-only compact MCP server for SAP ABAP ADT: the compact tools that change nothing
Mcp-abap-adt-compact-ro is an MCP integration. Read-only compact MCP server for SAP ABAP ADT: the compact tools that change nothing.
The published npm package is @mcp-abap-adt/compact-ro, version 20.0.0. Its declared MCP transport is stdio.
The package declares MCP_ENV_PATH: Path to the .env file that states the destination (the same as the --env-path argument). The file states SAP_URL and SAP_AUTH_TYPE (basic, snc or jwt); a jwt file also states SAP_GRANT_TYPE (authorization_code or none). Without this or --mcp, the server starts in tool-inspection-only mode: nothing is read from the working directory, and SAP_ variables in the process environment alone form no destination.; AUTH_BROKER_PATH: Base directory of service-keys/ and sessions/ for a named destination chosen with the --mcp argument (one directory; a list is not split). Default: ~/.config/mcp-abap-adt (Documents\mcp-abap-adt on Windows).; MCP_BROWSER: Browser for a JWT login: chrome, edge, firefox, system, headless or none.; MCP_BROWSER_AUTH_PORT: Callback port of the JWT browser login, 1-65535.; MCP_UNSAFE: Write a named destination's session to disk (sessions/ .env) instead of keeping it in memory.; SAP_CONNECTION_TYPE: Connection type: http or rfc. SNC needs rfc (and the SAP NW RFC SDK).; SAP_SYSTEM_TYPE (required): System type, required (here or as --system-type; no default, never guessed): the tools offered (e.g. Programs are onprem-only), the connector, and how the system's answers are read. Without it a destination does not start.; SAP_LANGUAGE: Logon language (ISO code, e.g. 'en', 'de')..
This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 20.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| MCP_ENV_PATH | Path to the .env file that states the destination (the same as the --env-path argument). The file states SAP_URL and SAP_AUTH_TYPE (basic, snc or jwt); a jwt file also states SAP_GRANT_TYPE (authorization_code or none). Without this or --mcp, the server starts in tool-inspection-only mode: nothing is read from the working directory, and SAP_ variables in the process environment alone form no destination. | Check documentation |
| AUTH_BROKER_PATH | Base directory of service-keys/ and sessions/ for a named destination chosen with the --mcp argument (one directory; a list is not split). Default: ~/.config/mcp-abap-adt (Documents\mcp-abap-adt on Windows). | Check documentation |
| MCP_BROWSER | Browser for a JWT login: chrome, edge, firefox, system, headless or none. | Check documentation |
| MCP_BROWSER_AUTH_PORT | Callback port of the JWT browser login, 1-65535. | Check documentation |
| MCP_UNSAFE | Write a named destination's session to disk (sessions/ .env) instead of keeping it in memory. | Check documentation |
| SAP_CONNECTION_TYPE | Connection type: http or rfc. SNC needs rfc (and the SAP NW RFC SDK). | Check documentation |
| SAP_SYSTEM_TYPE | System type, required (here or as --system-type; no default, never guessed): the tools offered (e.g. Programs are onprem-only), the connector, and how the system's answers are read. Without it a destination does not start. | Yes |
| SAP_LANGUAGE | Logon language (ISO code, e.g. 'en', 'de'). | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Claude, Codex, Cursor, VS Code, or any local MCP client to search, read, and send messages through the macOS Messages app.
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Local-first MCP server for semantic C# analysis & refactoring via Roslyn & MSBuildWorkspace.
_Join us in accelerating scientific discovery with AI and open-source tools!_