CAPforge

MCP server that makes your AI agent (Claude Code, Cursor, …) get SAP CAP/CDS right: scaffolding that follows real conventions, plus real validation against cds compile. The agent doesn't stop until the code compiles clean.

Website · npm · Leelo en español

It calls no LLM itself: your agent brings the model (BYOK). Zero inference cost, nothing leaves your machine.

Why

General-purpose models hallucinate CDS — annotation terms that don't exist, OData v2 syntax mixed into v4, invented fields — because there's barely any public CAP code in training data. CAPforge gives your agent the two things it's missing:

1. Curated, sourced knowledge — modern CAP/UI5 best practices distilled from official SAP docs (capire, OData vocabularies, reference samples), every rule with its source URL.

2. A real feedback loop — tools that run the actual compiler and linter and feed errors back until everything is green.

Tools

Normal flow: context → scaffold → write → validate → correct → until green. Migration flow: analyze_legacy → context (target) → propose map (REUSED / NEW / DISCARDED) → scaffold → validate.

Requirements

• Node.js 18+

• @sap/cds-dk available (globally or in the project) for cap_validate to work.

Install & try

npm install
node test-loop.js   # full-loop demo against the bundled sandbox

VS Code / SAP Business Application Studio

The extension/ folder ships a VS Code extension that registers the MCP server automatically (no mcp.json editing) for Copilot agent mode and any MCP client. Build it locally until it lands on the Marketplace / Open VSX:

cd extension && npm install && npx vsce package
code --install-extension capforge-0.1.3.vsix

Point the capforge.conventionsPath setting to your team's private conventions (Pro preview). BAS note: BAS installs extensions from Open VSX, but its AI assistant does not consume MCP servers natively yet — the extension is ready for the day it does.

Claude Code / Cursor

Register in Claude Code (project .mcp.json or global config):

{
  "mcpServers": {
    "capforge": {
      "command": "npx",
      "args": ["-y", "capforge"]
    }
  }
}

Load your team's private conventions (a preview of the Pro tier):

"env": { "CAPFORGE_CONVENTIONS": "PATH/to/team-conventions.md" }

Knowledge

• knowledge/ — canonical core: modern CAP/UI5 best practices (aspects, compositions, drafts, authorization, Fiori annotations, i18n, tooling, migration map), anchored to official SAP docs with cited sources.

• conventions/ — house profile: one team's style, overridable via CAPFORGE_CONVENTIONS. Wins over the core on style conflicts.

The conventions://cap resource serves both, combined, to the agent.

Free vs Pro

• Free (open source): all the tools + the canonical knowledge core.

• Pro: private team profile, codebase-aware generation at scale, migration mode, CI checks, support. Coming soon.

License

MIT.