A CLI that injects current SAP developer knowledge packs into an AI coding tool's context and wires up SAP's own MCP servers for it, shipped as a single binary through Homebrew, Scoop or GitHub Releases.
General-purpose coding assistants are trained on public content, so their advice on SAP technologies can be outdated or wrong, and sap-devs works by loading current knowledge packs into whichever assistant a developer already runs. Its init command sets it up, sync keeps the content current automatically, and inject writes SAP context into the configured AI tool and wires its SAP MCP servers. It ships as a single binary, installed through Homebrew, Scoop or a manual download from GitHub Releases rather than a service to sign up for.
A command line rather than a skill. One command injects SAP context into the AI tools that are configured, and a second is documented as the one that keeps the content current.
Run the sync. The README read on 2026-10-15 names no schedule and no list of supported assistants, so when the content is refreshed and which tool receives it are the developer's to establish.
Packaged knowledge that teaches a coding agent a framework
sap-devs injects up-to-date SAP developer knowledge into your AI coding tools, wires SAP MCP servers, and keeps content current automatically.
sap-devs# Install (Windows, Scoop):
# scoop bucket add sap-devs https://github.com/SAP-samples/sap-devs-cli.git
# scoop install sap-devs
#
# Install (macOS, Homebrew):
# brew tap SAP-samples/sap-devs-cli https://github.com/SAP-samples/sap-devs-cli.git
# brew install --cask sap-devs
#
# Install (Linux or manual): download from GitHub Releases, extract, add to PATH
sap-devs version
# First-time setup
sap-devs init
# Keep content current
sap-devs sync
# Inject SAP context into your AI tools
sap-devs injectAI coding assistants have become the default way developers write software. Tools like GitHub Copilot, Cursor, and Claude sit open in the background while developers work, answering questions and generating code on demand. By 2026 this shift is well underway, and it is reshaping how developers choose which technologies to build with.
The 2026 SAP Developer Survey shows that 31% of external developers are now using GenAI on production SAP projects - up from essentially zero just two years ago. More striking: 75% of those using these tools report a "profound positive impact" on their effectiveness. When asked about help resources, "consulting an LLM" ranked third, ahead of many traditional SAP channels. This isn't just developers using a new tool. This represents a fundamental shift in how technical decisions get made. The problem for SAP is straightforward. These AI tools were trained on general internet content, and their knowledge of SAP technologies is outdated, incomplete, and often wrong. A developer who asks their assistant how to build an SAP application gets bad advice, follows it, and wastes hours debugging code that should have worked. That experience is not neutral. It creates the impression that SAP is difficult, and it quietly steers developers toward alternatives.
sap-devs cli addresses this directly.
It is a small utility that developers install once. A single command delivers SAP's current best practices, recommended tools, and up-to-date guidance straight into the AI assistant the developer already uses, without changing how that tool looks or works. SAP knowledge becomes part of the developer's daily environment rather than a portal they have to remember to visit.
For developers already working in the SAP ecosystem, the benefit is immediate productivity. Accurate, opinionated guidance replaces the friction of correcting AI-generated mistakes. Curated resources and the latest release notes surface at the moment they are relevant, inside the coding environment, without any extra steps.
For developers new to SAP, this changes the first impression entirely. Historically, getting started with SAP required navigating extensive documentation and a steep learning curve. With sap-devs, a developer evaluating SAP for the first time receives clear, correct guidance from their AI assistant from day one. They do not need to know what questions to ask. The right answers show up anyway. That experience builds confidence and accelerates adoption.
For SAP's developer relations work, this opens a new distribution channel. SAP produces high-quality content: tutorials, blog posts, developer news, and curated learning paths. The challenge has always been getting that content in front of developers who are actively working on a problem. sap-devs solves that. SAP's best content reaches developers inside the tools they are already using, at the moment it matters most.
The broader opportunity is that AI assistants are fast becoming one of the most influential factors in which platforms developers choose. Platforms that integrate well into this workflow feel modern and worth learning. Platforms that do not feel like obstacles. Shipping accurate, current SAP knowledge into the AI tools developers use every day is one of the most direct ways SAP can influence that perception in 2026.
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a Developer Certificate of Origin (DCO) when they submit their first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
This project is provided "as-is": there is no guarantee that raised issues will be answered or addressed in future releases.
Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, v. 2 except as noted otherwise in the LICENSE file.
Features 1, Fixes 3
Shell hook reliability and output hygiene release.
tip install — detects your active shell (PowerShell, Bash, Zsh) and writes the hook to the correct profile file only, preventing duplicate tips when multiple profiles are sourced in the same session (e.g. Git Bash sources both .bashrc and .bash_profile). Auto-creates the profile file if it doesn't exist.sap-devs tip now outputs plain text when stdout is not a terminal (piped, redirected, or inside a script), instead of dumping raw escape codestip install now writes to a single detected profile rather than all existing ones, eliminating double-tip output on Git Bash for Windowsmcp install only wrote to one tool's config when multiple AI tools were detectedChanged 7
Changed 5
Changed 10
Changed 627
sap-devs events TODO as donesap-devs news command and add Friday Developer News hook remindersap-devs inject --status command with JSON and verbose output optionsSources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
artifact:sap-samples-sap-devs-cli