![\"npm](\"https://img.shields.io/npm/v/bas-mcp-addon?style=for-the-badge&color=CB3837&logo=npm&logoColor=white\")
\n ![\"npm](\"https://img.shields.io/npm/dm/bas-mcp-addon?style=for-the-badge&color=CB3837&logo=npm&logoColor=white\")
\n ![\"Node.js](\"https://img.shields.io/badge/Node.js-%E2%89%A520-339933?style=for-the-badge&logo=nodedotjs&logoColor=white\"){kind=icon}
\n ![\"MIT](\"https://img.shields.io/badge/License-MIT-75B900?style=for-the-badge\"){kind=icon}
\n\n AI-native ABAP development from GitHub Copilot Chat β directly against your SAP landscape
\n Inspect. Understand. Build. Test. Validate. Prepare for transport.
\n A destination-aware Model Context Protocol (MCP) bridge connecting SAP Business Application Studio, SAP ADT, VSP, and your GitHub Copilot coding agent.\n
\n
\n ![\"SAP](\"https://img.shields.io/badge/SAP-Business%20Application%20Studio-0A6ED1?style=flat-square&logo=sap&logoColor=white\"){kind=icon}
![\"GitHub](\"https://img.shields.io/badge/GitHub%20Copilot-Agent-000000?style=flat-square&logo=githubcopilot&logoColor=white\"){kind=icon}
![\"MCP](\"https://img.shields.io/badge/MCP-enabled-7B61FF?style=flat-square\"){kind=icon}
![\"SAP](\"https://img.shields.io/badge/SAP%20ADT-connected-0A6ED1?style=flat-square&logo=sap&logoColor=white\"){kind=icon}
![\"ABAP](\"https://img.shields.io/badge/ABAP-CDS%20%7C%20RAP-EA4AAA?style=flat-square\"){kind=icon}
\n π¦ Install Β·\n π€ Copilot Agent Β·\n π§ BAS Setup Β·\n π§° Tool Catalog Β·\n π©Ί Troubleshooting\n
\n\n## β‘ Quick start\n\n```sh\nnpm install --global bas-mcp-addon\nbas-vsp-mcp --setup\n```\n\nThen in SAP Business Application Studio:\n\n1. Open the Command Palette.\n2. Run **MCP: List Servers**.\n3. Start the server named after your selected BAS destination.\n4. In GitHub Copilot Chat, choose the best-fit bundled agent from the agent picker: **ABAP Developer**, **ABAP Runtime Debugger**, or **RAP Service Developer**.\n5. In the Chat tools picker, enable the server for that BAS destination.\n6. Ask Copilot what you want to inspect, build, test, or verify.\n\n**Prerequisite:** Node.js 20 or newer. If Go is not already available, the installer can provision the pinned supported Go release automatically.\n\n## π€ Available agents and skills\n\n**Agents:** Three user-invocable custom agents are included. Select the best fit from the agent picker in GitHub Copilot Chat, as shown in Quick start.\n\n| | Agent | Best for |\n| --- | --- | --- |\n| π§βπ» | **ABAP Developer** | General ABAP, CDS, and RAP implementation, validation, and transport-preparation tasks |\n| π | **ABAP Runtime Debugger** | Runtime incidents, dumps, logs, traces, debugger sessions, call graphs, and performance symptoms |\n| π | **RAP Service Developer** | RAP business objects, behavior implementations, projections, service definitions, service bindings, and OData validation |\n\n**Included skills:** `abap-development` Β· `abap-testing-quality` Β· `cds-development` Β· `rap-development` Β· `abap-debugging` Β· `abap-runtime-analysis` Β· `rap-service-delivery` Β· `sap-transport-release`\n\nIf the agents are not listed, install the optional agents and skills under `$HOME/.copilot` when prompted during an interactive global install, then reload BAS if needed. Repository-scoped installation instructions appear below.\n\n## β¨ Turn Copilot Chat into an SAP development cockpit\n\n`bas-mcp-addon` installs `bas-vsp-mcp`, discovers your BAS destinations, and exposes a curated SAP development toolset through MCP. Instead of manually switching between chat, terminal commands, repository searches, ADT screens, and SAP checks, describe the outcome you want and let the appropriate bundled agent coordinate the available tools.\n\nπ¬ Request β π Inspect β π§ Reason β π§βπ» Implement β π§ͺ Verify β π Report
\n\nThe workflow covers ABAP, CDS, RAP, repository analysis, table and query access, testing, ATC, application logs, transports, and controlled source changes. The live MCP tool list remains the source of truth for what your connected SAP system and active VSP mode expose.\n\n## π Feature highlights\n\n| | Feature | What it gives you |\n| --- | --- | --- |\n| π€ | **AI-driven ABAP development** | Ask for changes in natural language and let the bundled agents orchestrate inspection, implementation, runtime diagnosis, validation, and reporting. |\n| π§ | **BAS destination awareness** | Discover BAS destinations and create one isolated MCP server per selected SAP system. |\n| π | **Deep repository inspection** | Read source, search objects, grep packages, find definitions and references, compare source, inspect dependencies, and analyze impact. |\n| 𧩠| **CDS + RAP development** | Inspect CDS metadata and dependencies, model CDS artifacts, and build RAP business objects and services. |\n| ποΈ | **SAP data access** | Inspect DDIC structures, read table content, and execute controlled ABAP SQL queries against the connected system. |\n| βοΈ | **Create + edit ABAP objects** | Write or edit supported source objects, create packages and tables, syntax-check, and activate when explicitly requested. |\n| β | **Quality built into the flow** | Use local ABAP linting plus SAP syntax checks, ABAP Unit, ATC, editor diagnostics, and formatting. |\n| π | **Debugging + diagnostics** | Investigate dumps, traces, application logs, runtime failures, system capabilities, and installed components. |\n| π | **Transport-aware workflows** | Inspect transport requests and object lock context, and create transports when explicitly authorized. |\n| π | **Controlled SAP state changes** | State-changing actions require a known target and an explicit request; SAP authorizations still apply. |\n| 𧱠| **Destination isolation** | Each generated MCP server is tied to its own `BAS_VSP_DESTINATION`, helping prevent accidental cross-system execution. |\n| π‘οΈ | **Credential-safe configuration** | Credentials, cookies, usernames, passwords, and raw destination payloads are not written into MCP configuration. |\n\nThe catalog below documents 40 tool capabilities across source inspection, data, editing, quality, transports, and logs. Availability can vary by SAP system and VSP mode, so the live `tools/list` response is authoritative.\n\n## π What can the agent do?\n\n### π§βπ» Build and refactor\n\n- ABAP reports, classes, interfaces, and function groups\n- CDS definitions and dependency-aware changes\n- RAP business objects and services\n- Focused source edits with syntax validation\n\n### π Understand your SAP codebase\n\n- Search repository objects and packages\n- Find definitions and references\n- Compare implementations\n- Inspect class metadata and dependencies\n- Run CDS forward and reverse impact analysis\n\n### π§ͺ Validate quality\n\n- ABAP Unit\n- ATC checks\n- SAP syntax checks\n- Local `abaplint`\n- BAS editor and LSP diagnostics\n- Pretty-print source\n\n### π’ Work with the live SAP system\n\n- Read DDIC structures and table content\n- Execute ABAP SQL queries\n- Inspect system and component information\n- Read SLG1 application logs\n- Review and create transport requests\n\n## π§ Three agents, eight focused skills\n\nThe package ships with three custom agents plus eight task-focused Copilot Agent Skills:\n\n| | Skill | Best for |\n| --- | --- | --- |\n| π§βπ» | `abap-development` | Implementing and refactoring ABAP reports, classes, interfaces, and function groups |\n| β | `abap-testing-quality` | ABAP Unit, lint, LSP diagnostics, SAP syntax checks, and ATC |\n| 𧩠| `cds-development` | CDS modeling, dependency inspection, and consumer impact analysis |\n| π | `rap-development` | RAP business objects and service development |\n| π | `abap-debugging` | Dumps, logs, traces, and runtime failure diagnosis |\n| π¬ | `abap-runtime-analysis` | Incident triage, traces, debugger state, call graphs, and performance analysis |\n| π | `rap-service-delivery` | RAP service activation, publication, OData validation, and end-to-end runtime checks |\n| π | `sap-transport-release` | Dependency checks and transport preparation; release itself is intentionally unavailable here |\n\n## πΊοΈ How it fits together\n\nEach selected BAS destination becomes its own isolated MCP server identity. The MCP client discovers the live tools and schemas, the add-on routes calls to the correct VSP child, and VSP reaches SAP ADT through the selected BAS destination.\n\n## π‘ Example requests\n\nOnce the destination server is enabled in Copilot Chat, ask for outcomes instead of manually orchestrating individual SAP operations:\n\n> Find every reference to `ZCL_ORDER`, explain the impact of changing method `CREATE_ORDER`, and show me the callers before editing anything.\n\n> Fix the defect in `ZCL_PRICING`, add or update ABAP Unit coverage, run syntax checks and the available tests, and summarize exactly what passed or was skipped.\n\n> Inspect the dependencies and downstream consumers of this CDS view and tell me what would be affected by renaming the field.\n\n> Read company codes from `T001` for this destination and return `BUKRS`, `BUTXT`, `WAERS`, and `LAND1`.\n\n> Check the current object's transport context, prepare the change for transport, but do not release anything.\n\n## π Enterprise-friendly safety model\n\n| Guardrail | Behavior |\n| --- | --- |\n| π― **Explicit target** | SAP changes only proceed when the destination and required target details are known. |\n| π¦ **Explicit state change** | Activation, service publication, and transport creation happen only when requested and authorized. |\n| π§ͺ **Verification first** | The agent uses available lint, syntax, unit-test, ATC, and diagnostics workflows and reports what actually ran. |\n| π **SAP authorization remains authoritative** | The add-on does not bypass backend SAP permissions. |\n| π **Full VSP tool surface** | The proxy exposes every tool registered by the active VSP child, including transport tools; SAP authorizations and VSP safety checks still apply. |\n| 𧱠**Per-destination isolation** | Generated MCP entries are scoped to a single `BAS_VSP_DESTINATION`. |\n| π **No credentials in `mcp.json`** | Authentication material stays in BAS destination configuration rather than MCP config. |\n\n\n\n## π¦ Installation\n\nInstall globally from a BAS dev space:\n\n```sh\nnpm install --global bas-mcp-addon\n```\n\nThe installer handles two setup tasks automatically:\n\n- Looks for Go in `GO_BINARY`, `PATH`, or the package-local Go installation. If none is available, it downloads and installs the pinned supported Go release without prompting.\n- Uses the package's checksum-verified patched VSP binary for the current platform. A remote download is the fallback only when the package has no bundled asset.\n\nWith `H2O_URL` set, an interactive install opens a checkbox picker with no destinations selected by default. Use **Space** to choose destinations and **Enter** to confirm. Press **a** to toggle all destinations (select all if any are unchecked; otherwise clear the selection). Confirming with none selected removes this add-on's managed MCP entries. When the `cf` CLI 8.18 or newer is authenticated to a targeted space, setup first offers an optional import from that space's Destination service; type **y** then **Enter** to include it, or press **Enter** to skip. Accepted CF and BAS destinations appear together in the picker. npm may run its install hook without an interactive terminal, even when the shell is interactive; in that case, selection is skipped without changing MCP config.\n\nThe setup report uses icons and terminal colors; set `NO_COLOR=1` to disable ANSI colors. The table is a weather report, not a bouncer: green **PASS** means the ADT probe responded, red **FAIL** means it failed, and yellow **SKIPPED** means it was skipped. Probe failures do not block MCP registration or startup for destinations you select.\n\nRun `bas-vsp-mcp --setup` later to change the selection or remove generated entries. Use `--npx` to make the generated entries start the pinned package through npm instead of relying on a global `bas-vsp-mcp` command.\n\nIf a setup step is skipped or fails, rerun it from an interactive BAS terminal:\n\n```sh\nbas-vsp-mcp --setup\n```\n\nTo configure without a global install, run the guided setup directly through npm:\n\n```sh\nnpx --yes --ignore-scripts --package=bas-mcp-addon bas-vsp-mcp --setup --npx\n```\n\nThis lists discovered systems in the same checkbox picker, with nothing selected by default. Use **Space** to choose destinations, **Enter** to confirm, and **a** to toggle all (select all if any are unchecked; otherwise clear the selection). It writes MCP entries that launch the selected servers through npx. The entries pin the package version used during setup, and `--ignore-scripts` avoids running the install-time wizard a second time. After setup, in BAS run **MCP: List Servers**, select each chosen destination, and choose **Start Server**.\n\nFor a non-interactive installation or a platform without a published VSP asset, provide a trusted binary override:\n\n```sh\nBAS_VSP_BINARY=/path/to/vsp npm install --global bas-mcp-addon\n```\n\nAt the end of a global install, the color-coded summary shows the MCP config path, each generated entry name, destination/client/authentication, launch command, and environment key names (not values). The installer does not open an editor automatically; in BAS/VS Code:\n\n1. Open the Command Palette.\n2. Run **MCP: List Servers**.\n3. Select the generated server name shown in the report and choose **Start Server**.\n4. Use **MCP: Open User Configuration** to inspect or edit the generated entries. Each entry is isolated to its destination.\n\n\n\n## π€ GitHub Copilot ABAP agents and skills\n\nThe package includes three user-invocable custom agents (**ABAP Developer**, **ABAP Runtime Debugger**, and **RAP Service Developer**) and eight task-focused Agent Skills for GitHub Copilot in BAS.\n\n### π§ How the primary ABAP Developer agent works\n\n1. **Understand the request.** Establish the expected behavior and, for SAP changes, the destination, package, and transport or temporary target. Ask only when a material detail is missing.\n2. **Inspect before editing.** Read relevant source, tests, callers, dependencies, and conventions; query the active MCP server's live `tools/list` and use its exact destination-prefixed tools and schemas.\n3. **Implement with behavior in mind.** Add or refine an ABAP Unit assertion first when an executable regression test is available, then make the smallest change that meets the request.\n4. **Verify with available checks.** Use `LintABAP` for caller-supplied source, BAS editor LSP diagnostics when configured, and SAP `SyntaxCheck`, `RunUnitTests`, and `RunATCCheck` when exposed and relevant. Lint and syntax checks do not replace behavior tests.\n5. **Protect SAP state.** Only make requested changes. Activate objects or publish services only when asked; create transports only when explicitly authorized. Release and deletion of transports are unavailable through this add-on.\n6. **Report observed results.** Summarize changed objects and actual validation, activation, or publication outcomes. Identify skipped checks and exact blockers; never claim a check passed if it did not run.\n\n### 𧩠Included Agent Skills\n\n| | Skill | Focus |\n| --- | --- | --- |\n| π§βπ» | `abap-development` | Implement and refactor ABAP reports, classes, interfaces, and function groups. |\n| β | `abap-testing-quality` | ABAP Unit behavior tests, lint, LSP diagnostics, syntax checks, and ATC. |\n| 𧩠| `cds-development` | Model CDS definitions and inspect dependencies and consumers. |\n| π | `rap-development` | Build RAP business objects and services; publish only when requested. |\n| π | `abap-debugging` | Diagnose dumps, application logs, traces, and runtime failures. |\n| π¬ | `abap-runtime-analysis` | Analyze incidents, traces, debugger state, call graphs, and performance symptoms. |\n| π | `rap-service-delivery` | Validate RAP service bindings, activation, publication, and end-to-end OData behavior. |\n| π | `sap-transport-release` | Check dependencies and prepare changes for transport; release is not available here. |\n\n### π₯ Install for your BAS user\n\nAfter destination setup, the installer prints a π€ notice that it is waiting for confirmation, then offers to install the bundled agents and all eight skills under `$HOME/.copilot`. Press **Enter** to install; type **n** then **Enter** to skip. Declining leaves those files unchanged.\n\nThese user-level customizations are available across workspaces opened by the same BAS user in the same dev space. Copilot must be available in BAS and may need a window reload to discover new files. A non-interactive install skips the optional prompt; `npm install --ignore-scripts` skips the postinstall wizard entirely.\n\nOn reinstall or package upgrade, unchanged add-on-managed files are updated. Existing customizations and files edited since the previous install are preserved; postinstall reports paths that need manual review instead of overwriting them.\n\n### ποΈ Add the agents and skills to a repository\n\nTo commit repository-scoped customizations, copy the packaged files from the BAS workspace root without overwriting existing files:\n\n```sh\nADDON_ROOT=\"$(npm root -g)/bas-mcp-addon\"\nmkdir -p .github/agents .github/skills\ncp -n \"$ADDON_ROOT/.github/agents/\"*.agent.md .github/agents/\ncp -Rn \"$ADDON_ROOT/.github/skills/.\" .github/skills/\n```\n\nReview skipped or conflicting files and merge changes manually. `LintABAP` analyzes caller-supplied source in memory; it does not read workspace files. `vsp lsp --stdio` supplies editor diagnostics separately and does not appear in `tools/list`.\n\n\n\n## π§ BAS setup\n\n`bas-vsp-mcp --setup` reads BAS destination names from `H2O_URL/api/listDestinations`, then gives each destination's `/sap/bc/adt/discovery` endpoint a quick knock through the BAS proxy. HTTP 2xx, 401, and 403 count as reachable; other responses and network failures are reported but do not exclude discovered destinations from the selection list or prevent startup when selected.\n\nIf the `cf` CLI is version 8.18 or newer and authenticated to a targeted space, setup offers an opt-in import from that space's SAP Destination service. It does not create service keys unless you accept. The imported records are limited to the current space and are merged with BAS destinations for selection. OnPremise destinations require choosing a Connectivity service instance; runtime traffic uses that service's proxy, and PrincipalPropagation uses the current CF user's token. Internet destinations use the configured HTTP(S) proxy environment. Setup stores only service-instance/key references in `mcp.json`, not the service-key credentials. At runtime the generated entry verifies the active CF space and resolves those references. Setup removes an add-on-created key only when no remaining CF entry references it and the CLI is targeted to the key's recorded space; keys are left untouched when the space cannot be verified.\nCloud Foundry HTTP destination probes use forward-form HTTP requests, not CONNECT tunnels; SAP Connectivity requires HTTP from the application to its proxy. OnPremise requests are canceled when the client disconnects or the runtime route closes.\n\nInteractive npm install and `bas-vsp-mcp --setup` both use a checkbox picker with no destinations selected by default. Use **Space** to choose destinations, **Enter** to confirm, and **a** to toggle all (select all if any are unchecked; otherwise clear the selection). Confirming with none checked removes this package's generated MCP entries. Non-interactive installs skip destination selection without changing MCP config. Run the interactive setup command above; add `--npx` when the package is not installed globally.\n\nSetup tidies its own footprint: it reconciles MCP entries managed by this package and removes its legacy `basVspMcp_*` entries. Existing unrelated MCP servers and top-level configuration such as `inputs` stay untouched.\n\n### π BAS destination example\n\nFirst, give BAS a route to your backend: create the destination in **BTP Cockpit β Connectivity β Destinations** in the subaccount where BAS runs.\n\nThe sample values sketch an on-premise ABAP backend routed through SAP Cloud Connector; swap in the URL, proxy type, and authentication configured for your landscape.\n\n| Destination field | Example | Notes |\n| --- | --- | --- |\n| `Name` | `DEMO_ABAP` | Unique BAS destination name. It becomes both `BAS_VSP_DESTINATION` and the generated MCP server name. |\n| `Type` | `HTTP` | ADT is an HTTP service. |\n| `URL` | `https://abap.example.com:44300` | Backend URL exposed through the configured route. |\n| `Proxy Type` | `OnPremise` | Use `OnPremise` for Cloud Connector; use `Internet` for a directly reachable public endpoint. |\n| `Authentication` | `PrincipalPropagation` | Example only; choose an authentication method configured for the backend and Cloud Connector. |\n| `sap-client` | `100` | SAP client to target. The add-on defaults to `001` if omitted. |\n| `HTML5.DynamicDestination` | `true` | BAS destination property shown in the supplied sample. |\n| `WebIDEEnabled` | `true` | Exposes the destination to BAS development tools. |\n| `WebIDEUsage` | `dev_abap,odata_abap` | Include `dev_abap` for ABAP development; add other usages required by your BAS scenario. |\n| `CloudConnectorLocationId` | `DEMO-LOCATION` | Optional; set only when the Cloud Connector uses a location ID. |\n\nFor on-premise systems, configure Cloud Connector access to the backend host and port first. Keep credentials and authentication material in the BAS destination configuration; never put them in `mcp.json`.\n\nThink of `H2O_URL` as BAS's front door: it must point to the endpoint serving `/api/listDestinations`, not to the SAP backend.\n\nThe `/api/listDestinations` response is a JSON array of destination records, like the provided `dests.sample.json`. A representative record:\n\n```json\n{\n \"Type\": \"HTTP\",\n \"HTML5.DynamicDestination\": \"true\",\n \"Authentication\": \"PrincipalPropagation\",\n \"WebIDEEnabled\": \"true\",\n \"ProxyType\": \"OnPremise\",\n \"sap-client\": \"100\",\n \"Name\": \"DEMO_ABAP\",\n \"WebIDEUsage\": \"dev_abap,odata_abap\",\n \"Host\": \"https://abap.example.com:44300\",\n \"WebIDEExposedHost\": \"abap.example.com:44300\"\n}\n```\n\nThe BAS editor calls the backend address URL; the sample-style list response may report it as `Host`. Discovery needs a non-empty `Name`, reads `Authentication` and `sap-client` case-insensitively, and accepts these fields either at the record root or under `Properties`.\n\nA destination name must start with a letter or digit and contain only letters, digits, `.`, `_`, or `-`.\n\nThe add-on probes `http://