vibing-steampunk

Vibing Steampunk (vsp) is an MCP server that provides AI-agentic access to SAP ABAP environments via the ADT APIs. It enables Claude and other AI assistants to read code, write code, debug, deploy, and run tests in SAP ABAP systems through natural language or a DSL for automation. The server exposes a set of ABAP-oriented tools and commands that let you inspect objects, export/import packages, run reports, debug sessions, and perform system-level operations from an MCP-enabled workflow. Use its capabilities to iterate on ABAP development with AI guidance, while controlling access and operations through your MCP client.

To start using Vibing Steampunk, connect your MCP client to the vibing-steampunk MCP server and initiate tasks such as reading source, editing methods, exporting packages, or running ABAP reports. The server is designed to integrate with your existing SAP landscape, enabling AI-assisted development tasks that would normally require manual SAP GUI interactions or multiple manual steps. As you issue commands, the AI-assisted tooling will provide responses, code snippets, and step-by-step actions you can execute within your SAP environment.

Prerequisites:

• Node.js (LTS) and npm installed on your machine or the hosting environment where the MCP server will run
• Access to the SAP ABAP environment via ADT (as supported by Vibing Steampunk)

Installation steps:

1. Clone or download the Vibing Steampunk MCP server repository.
2. Navigate to the project directory in your terminal.
3. Install dependencies: npm install
4. Start the MCP server: npm run start or, if a direct node start script is provided by the repository: node server.js
5. Verify the server is running by checking the startup logs or hitting the MCP server health endpoint (if documented).

Configuration (optional):

• If you require environment-specific settings (e.g., SAP endpoints, authentication tokens), set them in your environment or a provided .env file as applicable to the project.
• Ensure network access to your SAP ADT APIs and any required firewall rules are configured so the MCP client can communicate with Vibing Steampunk.

Tips and considerations:

• Confirm SAP ADT connectivity and permissions before enabling AI-driven edits or package operations.
• If you use transportable edits or advanced safety features, review the in-repo documentation or release notes for compatibility with your SAP system version.
• Monitor startup logs for any dependency or connectivity issues and verify that the MCP client is using the correct server name (vibing-steampunk) when issuing commands.
• For security, avoid exposing SAP credentials in logs; prefer environment-managed tokens or secure vaults where supported.
• If you encounter issues, consult the Reviewer Guide and release notes sections in the repository for troubleshooting steps and known limitations.