Vibing Steampunk
vs-punk: ADT to MCP bridge - Vibe code in ABAP / AMDP
What is Vibing Steampunk?
Vibing Steampunk is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to vs-punk: adt to mcp bridge - vibe code in abap / amdp
vs-punk: ADT to MCP bridge - Vibe code in ABAP / AMDP
This server falls under the Coding Agents category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- vs-punk: ADT to MCP bridge - Vibe code in ABAP / AMDP
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx vibing-steampunkConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Vibing Steampunk
Vibing Steampunk (vsp) is an ADT-to-MCP bridge that connects AI assistants directly to SAP ABAP Development Tools (ADT), enabling vibe-coding in ABAP and AMDP. It exposes over 100 SAP development operations including reading and editing ABAP class sources, running unit tests, executing ATC code checks, deploying objects, and debugging with breakpoints — all accessible through a single MCP interface. Developers working on SAP systems use it to let Claude or other LLMs write, refactor, test, and deploy ABAP code with full awareness of the SAP repository, significantly accelerating enterprise development workflows.
Prerequisites
- Access to a running SAP ABAP system with ADT (ABAP Development Tools) enabled on the server
- vsp binary downloaded from the GitHub releases page or built from source (Go toolchain required for build)
- SAP_URL, SAP_USER, and SAP_PASSWORD credentials for the target SAP system
- An MCP client such as Claude Desktop, Claude Code, or VS Code with an MCP extension
Download the vsp binary
Download the prebuilt binary for your platform from the GitHub releases page. On Linux/macOS, make it executable. On Windows, place vsp.exe in a folder on your PATH.
# Linux example
curl -LO https://github.com/oisee/vibing-steampunk/releases/latest/download/vsp-linux-amd64
chmod +x vsp-linux-amd64
mv vsp-linux-amd64 /usr/local/bin/vspInitialize configuration
Run 'vsp config init' to generate example configuration files in the current directory. This creates .env.example, .vsp.json.example, and .mcp.json.example as starting points.
vsp config initConfigure SAP system credentials
Copy the example .vsp.json to .vsp.json and fill in your SAP system URL, username, client number, and other connection details. You can also use environment variables instead.
{
"default": "dev",
"systems": {
"dev": {
"url": "https://your-sap-host:44300",
"user": "DEVELOPER",
"client": "001"
}
}
}Test connectivity to the SAP system
Verify that vsp can reach the SAP ADT endpoint by searching for an ABAP object. A result list confirms the connection is working.
vsp -s dev search "ZCL_*" --type CLAS --max 10Add the MCP server to your client configuration
Register vsp as an MCP server in Claude Desktop or Claude Code. Use 'hyperfocused' mode (SAP_MODE=hyperfocused) for minimal token usage — it exposes a single universal SAP() tool.
{
"mcpServers": {
"abap-adt": {
"command": "/usr/local/bin/vsp",
"env": {
"SAP_URL": "https://your-sap-host:44300",
"SAP_USER": "DEVELOPER",
"SAP_PASSWORD": "yourpassword",
"SAP_CLIENT": "001",
"SAP_MODE": "hyperfocused"
}
}
}
}Restart your MCP client
Restart Claude Desktop (or reload your VS Code window) so the new MCP server definition is picked up. The SAP tools will then be available in the assistant.
Vibing Steampunk Examples
Client configuration
Minimal Claude Desktop config using environment variable credentials and hyperfocused tool mode. Replace the URL and credentials with your own SAP system details.
{
"mcpServers": {
"abap-adt": {
"command": "/usr/local/bin/vsp",
"env": {
"SAP_URL": "https://your-sap-host:44300",
"SAP_USER": "DEVELOPER",
"SAP_PASSWORD": "yourpassword",
"SAP_CLIENT": "001",
"SAP_MODE": "hyperfocused"
}
}
}
}Prompts to try
These prompts work after the vsp MCP server is connected and your SAP system is reachable.
- "Read the source of ABAP class ZCL_MY_ORDER_HANDLER"
- "Run unit tests for all objects in package $ZDEV and show me the failures"
- "Check ATC code quality violations for class ZCL_MY_CLASS and suggest fixes"
- "Deploy the local file zcl_test.clas.abap to the $TMP package on my dev system"
- "Show the call graph for ZCL_TRAVEL and identify any cross-boundary dependencies"Troubleshooting Vibing Steampunk
Connection refused or TLS error when connecting to SAP
Set SAP_INSECURE=true in the env block if your SAP system uses a self-signed certificate. For production systems, install the SAP system certificate in your OS trust store instead.
Edit operations fail with 'transportable package not allowed'
Set SAP_ALLOW_TRANSPORTABLE_EDITS=true and optionally restrict which transport requests are allowed via SAP_ALLOWED_TRANSPORTS (e.g., 'DEVK*'). Only set these in development systems.
Too many tools slow down the LLM or exceed tool count limits
Switch to hyperfocused mode by setting SAP_MODE=hyperfocused. This exposes a single universal SAP() tool with ~200 schema tokens instead of 100–147 individual tools.
Frequently Asked Questions about Vibing Steampunk
What is Vibing Steampunk?
Vibing Steampunk is a Model Context Protocol (MCP) server that vs-punk: adt to mcp bridge - vibe code in abap / amdp It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Vibing Steampunk?
Follow the installation instructions on the Vibing Steampunk GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Vibing Steampunk?
Vibing Steampunk works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Vibing Steampunk free to use?
Yes, Vibing Steampunk is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
Vibing Steampunk Alternatives — Similar Coding Agents Servers
Looking for alternatives to Vibing Steampunk? Here are other popular coding agents servers you can use with Claude, Cursor, and VS Code.
Dify
★ 142.2kProduction-ready platform for agentic workflow development.
Ruflo
★ 54.0k🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, self-learning swarm intelligence, RAG integrat
Goose
★ 45.7kan open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
Antigravity Awesome Skills
★ 38.3kInstallable GitHub library of 1,400+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
AgentScope
★ 25.5kBuild and run agents you can see, understand and trust.
Serena
★ 24.5kA coding agent toolkit that provides IDE-like semantic code retrieval and editing tools, enabling LLMs to efficiently navigate and modify codebases using symbol-level operations instead of basic file reading and string replacements.
Browse More Coding Agents MCP Servers
Explore all coding agents servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Vibing Steampunk in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Vibing Steampunk?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.