Vibing Steampunk (vsp) MCP
vsp is an ADT to MCP bridge: an agent reads and writes ABAP code, runs tests and drives the SAP debugger with no server install
- 528 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Writes and changes ABAP source and objects in the SAP system, runs tests and installs handlers onto the system with vsp install
- Uses the SAP user's login and password or session cookies and gives the agent that user's rights, up to transport management with expert tools enabled
- The debugger halts program execution in the system, and reading logs, spool and tables exposes business data to the agent
Install
- Works in
Manual install
curl -LO https://github.com/oisee/vibing-steampunk/releases/latest/download/vsp-linux-amd64Then chmod +x. For Windows and macOS take the binary from the releases page. Alternative: git clone and make build.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Writes and changes ABAP source and objects in the SAP system, runs tests and installs handlers onto the system with vsp install
- Uses the SAP user's login and password or session cookies and gives the agent that user's rights, up to transport management with expert tools enabled
- The debugger halts program execution in the system, and reading logs, spool and tables exposes business data to the agent
This is third-party code. Review the repository files before installing.
What it does
Vibing Steampunk (vsp) is a Go binary that opens an SAP system to agents through MCP. The agent reads and writes ABAP source, searches objects, runs unit tests, creates objects and analyzes failures, and vsp works through ADT, the interfaces Eclipse relies on. It needs a system with ADT enabled, 7.50 upwards, the available surface depends on the release, and vsp compat reports it per system. RAP requires S/4 and AMDP requires HANA. The README describes a full ABAP debugger: breakpoints, attach, stepping, call stack and variables. It runs over a pinned RFC session or over HTTPS with nothing installed on the server and no SAP SDK. Then come post-mortem tools: dumps --explain reads the whole ST22 document, plus the application log, spool and jobs, the cluster tables BALDAT, INDX and STXL and a byte-exact read of the SMW0 MIME repository. Tool counts vary by mode: focused has 98, expert 148, and hyperfocused has one universal SAP(action, target, params) tool at about 200 schema tokens instead of 40 thousand. There is also a plain command-line mode with no MCP. Eight agents work with vsp, among them Claude Code, Gemini CLI, GitHub Copilot and OpenAI Codex.
Who it is for. ABAP developers and SAP consultants who want development, debugging and failure analysis through an agent on their development systems.
Good fit when
- The agent has to read the class ZCL_MY_CLASS with its dependency contracts and make a surgical edit
- You are analyzing a failure: dumps --explain collects the message, variables and source line from ST22
- ABAP debugging runs as a loop of breakpoint, attach, steps and variable inspection through the agent
- You want to save tokens on the tool schema: hyperfocused mode replaces 148 tools with one
Not a fit when
- You need SAP data access through OData: the author has a separate OData to MCP bridge for that
- The system does not support ADT or is older than 7.50: the available surface depends on the release
- You are working on a production system without write permission: writing and debugging need developer rights
Example request
Read the class ZCL_TRAVEL with its dependency contracts, find the cause of the ST22 dump and propose a fix without writing to the systemMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
SAP_URLrequired- Address of the SAP system's web interface as in Fiori Launchpad, not the message server address
SAP_USER- SAP user for basic authentication
SAP_PASSWORDsecret- SAP user password, needed for basic authentication
SAP_CLIENT- SAP client number
Limitations
- Needs ADT enabled, system 7.50 or newer. RAP works only on S/4, AMDP only on HANA, and some ADT resources present on S/4 are absent on ERP.
- Basic authentication needs a user password, and if a password cannot be set, the fallback is a cookies.txt file with cookies from a browser session, which expire.
- Installing ZADT_VSP and abapGit on a system is done with vsp install commands and changes the SAP system.
- Some capabilities, such as gCTS, revision history and i18n, are available only in expert mode.
How to disable. Remove the server entry from .mcp.json or the agent's settings and delete the vsp binary. Delete the cookies.txt file and the .env with credentials separately. If ZADT_VSP or abapGit were installed, remove them with SAP tools.
FAQ
How do I connect SAP to Claude Code through vsp?
Download the vsp binary from the releases, run vsp config init and fill .vsp.json, .env and .mcp.json, then test the connection with an object search. The server starts as MCP by default, and in .mcp.json the system corresponds to an entry with the arguments -s dev.
What do I need to install on the SAP server?
Nothing for reading, editing, tests and debugging: vsp works through ADT and the debugger runs over RFC or HTTPS without any installation. Extras such as the ZADT_VSP handler and abapGit are installed with vsp install zadt-vsp and vsp install abapgit.
What is the difference between focused, expert and hyperfocused modes?
Focused has 98 tools, expert 148, and hyperfocused gives one universal tool SAP(action, target, params). Its schema takes about 200 tokens instead of roughly 40 thousand, and the mode is recommended for most setups.
How do I log in without a password?
The authors describe cookie login: SAP_SESSIONID_SYS_CLI and sap-usercontext values are saved to cookies.txt in the Netscape format. Session cookies expire on timeout, so the values must be refreshed.
Which agents work with vsp?
Eight are documented: Gemini CLI, Claude Code, GitHub Copilot, OpenAI Codex, Qwen Code, OpenCode, Goose and Mistral Vibe. Configs are in docs/cli-agents, along with Russian and Ukrainian versions of the guide.
Discussion
No questions or reviews yet.
Related
MCP serversmcp-abap-adt opens SAP ECC, S/4HANA and BTP ABAP repositories to an agent: analysis, creation and editing of objects through ADT.
ARC-1: an MCP server for SAP ABAP systems, safe by default, with reading, code edits, transports and checks through ADT.
MCP server to SAP ABAP through ADT: an agent reads code of programs, classes, tables and CDS and searches objects in the system
An MCP server for SAP ABAP: an agent finds objects, reads and edits sources, checks syntax and handles transports through ADT
A debugger MCP server: the agent sets breakpoints, steps through code and reads variables of a live program over DAP.
Codev runs a GitHub issue through the SPIR protocol: specification, plan, implementation and review, with parallel builders.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Vibing Steampunk (vsp) (this card) | no | key is optional | 528 | |
| mcp-abap-adt | no | OAuth | 106 | another ADT bridge, while vsp adds an RFC debugger, dump analysis and a one-tool mode |
| ABAP ADT MCP Server | no | API key | 209 | another MCP server for ABAP, while vsp is written in Go and includes a debugger and a command-line mode |
README in short
The README opens with a tour of the latest releases: MIME repository, cluster tables, dump analysis, log and spool. Then it shows the debugger over RFC, tool modes, a Windows quick start with VS Code, the list of agents and the CLI mode commands.