Skip to content

docs: SAP MCP proxy demo (Vaara in front of community SAP MCP servers)#101

Merged
vaaraio merged 1 commit into
mainfrom
docs/sap-mcp-proxy-demo
May 19, 2026
Merged

docs: SAP MCP proxy demo (Vaara in front of community SAP MCP servers)#101
vaaraio merged 1 commit into
mainfrom
docs/sap-mcp-proxy-demo

Conversation

@vaaraio
Copy link
Copy Markdown
Owner

@vaaraio vaaraio commented May 19, 2026

Adds examples/sap-mcp-proxy-demo/ with README + Claude Code config showing how to insert Vaara in front of an existing community SAP MCP server. Reader brings SAP. Three-step recipe.

Adds examples/sap-mcp-proxy-demo/ with a README walkthrough and a Claude Code MCP config example showing how to insert Vaara's runtime governance proxy in front of an existing community SAP MCP server (mario-andreschak/mcp-abap-abap-adt-api, SAP/mdk-mcp-server, lemaiwo/btp-sap-odata-to-mcp-server, or any other listed in marianfoo/sap-ai-mcp-servers).

The demo targets an SAP architect already running Claude Code against a SAP MCP server and a real SAP system (BTP, S/4HANA, NetWeaver). It does not include or stub a SAP backend. The reader brings the SAP side; the demo brings the Vaara wiring.

Three-step recipe: pip install vaara, replace the existing Claude Code MCP config entry with the Vaara proxy command in front of the same upstream MCP server, restart Claude Code. Every tools/call routes through Vaara's interception pipeline before reaching the upstream. Audit trail accumulates in a local SQLite DB and exports as AI Act Article 12 evidence via vaara compliance report / vaara trail export.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 19, 2026

Warning

Rate limit exceeded

@vaaraio has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 30 minutes and 10 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cdcf7729-f8cc-4c48-b4be-afbfac6dacea

📥 Commits

Reviewing files that changed from the base of the PR and between c6f1cca and 543bad2.

📒 Files selected for processing (2)
  • examples/sap-mcp-proxy-demo/README.md
  • examples/sap-mcp-proxy-demo/claude_code_config.example.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/sap-mcp-proxy-demo

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@vaaraio vaaraio merged commit a6f15a6 into main May 19, 2026
10 checks passed
@vaaraio vaaraio deleted the docs/sap-mcp-proxy-demo branch May 19, 2026 15:03
vaaraio added a commit that referenced this pull request May 19, 2026
…ME section (#105)

Two problems shipped in #100 and #101 that were fixed here:

1. README's MCP proxy code example used `npx --upstream-arg @sap/adt-mcp-server`, a fictional npm package. The MCP proxy block was also buried as a third-tier subsection under Framework integrations, despite v0.21.0 being the headline ship and having two worked demos.

2. SAP demo's example config used `npx -y @mario-andreschak/mcp-abap-abap-adt-api`, which is not published on npm. The real install path for that server is git clone + npm install + npm run build, then run with `node /path/to/dist/index.js`.

Fixes:

- README: removed the buried `### MCP proxy` subsection under Framework integrations and added a top-level `## MCP proxy` section between TypeScript client and OVERT. Uses `@sap/mdk-mcp-server` (verified on npm at version 0.3.7) as the one-line example. Links both demo folders.

- examples/sap-mcp-proxy-demo/claude_code_config.example.json: primary `sap-mdk-via-vaara` block now uses the real `@sap/mdk-mcp-server` invocation. Sibling `_alternative_abap_adt` block uses the real `node /PATH_TO_YOUR/mcp-abap-abap-adt-api/dist/index.js` invocation. Sibling `_alternative_btp_odata` block clarified as clone+build.

- examples/sap-mcp-proxy-demo/README.md: prereqs section names each upstream's real install path. Before/After config blocks now show the real MDK invocation. Note steering ABAP/OData readers to the alternative blocks in the example config.

Verified upstreams via npm registry and GitHub API: `@sap/mdk-mcp-server` is published, official, Apache-2.0; `mario-andreschak/mcp-abap-abap-adt-api` is on GitHub (134 stars, MIT) but not on npm; `SAP/mdk-mcp-server` repo is Apache-2.0, 31 stars.

Co-authored-by: vaaraio <267591518+vaaraio@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant