Skip to content
Back to search

sap-b1-briefing-mcp

MCP server exposing SAP Business One-style sales data (mock-backed) to Claude for hands-free customer-visit briefings

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mukeshdas-saavantus--sap-b1-briefing-mcp/badge.svg)](/listings/mukeshdas-saavantus--sap-b1-briefing-mcp)

HTML

<a href="/listings/mukeshdas-saavantus--sap-b1-briefing-mcp"><img src="/api/listings/mukeshdas-saavantus--sap-b1-briefing-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npm install
npm run build

Add this to Claude Desktop's config (Windows: `%APPDATA%\Claude\claude_desktop_config.json`), adjusting the path if this project lives somewhere else — Claude Desktop requires absolute paths here:

{
  "mcpServers": {
    "sap-b1-demo": {
      "command": "node",
      "args": ["C:\\Users\\Mukesh Kumar\\Desktop\\Mukesh-Claude\\dist\\index.js"]
    }
  }
}

(Also at [`.claude-desktop/claude_desktop_config.sample.json`](.claude-desktop/claude_desktop_config.sample.json).)

Restart Claude Desktop, then see [`docs/demo-script.md`](docs/demo-script.md) for a scripted walkthrough, including the "misspoken customer name" moment the original demo highlighted.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 128 lines
  1. # SAP B1 Briefing MCP Server
  2. An MCP (Model Context Protocol) server that lets Claude answer sales-prep questions —
  3. recent orders, overdue invoices, stock availability, follow-up suggestions — about SAP
  4. Business One-style customer data, conversationally.
  5. Inspired by Tom Cenens' LinkedIn article
  6. ["From the Driver's Seat to SAP: A Real-World AI Demo"](https://www.linkedin.com/pulse/from-drivers-seat-sap-business-one-real-world-ai-demo-tom-cenens-5xxbe),
  7. which paired Claude's voice mode with a commercial SAP Business One MCP connector
  8. ("Amista AI Data Enabler") for hands-free customer briefings from a car. This project is an
  9. original implementation — it does not use or copy that product — built directly against the
  10. shape of SAP Business One's own Service Layer data, with mock data standing in for a real
  11. system.
  12. ## What this is (and isn't), today
  13. - **Data**: mock, in-memory data shaped like real SAP Business One Service Layer entities
  14. (`BusinessPartners`, `Orders`, `Invoices`, `Items`), not a live SAP connection. See
  15. [`src/data/sap-service-layer/README.md`](src/data/sap-service-layer/README.md) for what a
  16. real backend would need.
  17. - **Transport**: local stdio only, for Claude Desktop. No remote hosting, no mobile/CarPlay
  18. replication of the original demo (that needs a hosted server with OAuth — a documented
  19. future phase, not built here).
  20. - **Tools**: read-only. No tool can modify SAP data.
  21. ## Setup
  22. ```powershell
  23. npm install
  24. npm run build
  25. ```
  26. Add this to Claude Desktop's config (Windows: `%APPDATA%\Claude\claude_desktop_config.json`),
  27. adjusting the path if this project lives somewhere else — Claude Desktop requires absolute
  28. paths here:
  29. ```json
  30. {
  31. "mcpServers": {
  32. "sap-b1-demo": {
  33. "command": "node",
  34. "args": ["C:\\Users\\Mukesh Kumar\\Desktop\\Mukesh-Claude\\dist\\index.js"]
  35. }
  36. }
  37. }
  38. ```
  39. (Also at [`.claude-desktop/claude_desktop_config.sample.json`](.claude-desktop/claude_desktop_config.sample.json).)
  40. Restart Claude Desktop, then see [`docs/demo-script.md`](docs/demo-script.md) for a scripted
  41. walkthrough, including the "misspoken customer name" moment the original demo highlighted.
  42. ## Development
  43. ```powershell
  44. npm run dev # run directly with tsx, no build step
  45. npm test # vitest
  46. npm run lint # eslint
  47. npm run typecheck # tsc --noEmit
  48. npm run format # prettier --write
  49. ```
  50. `.env.example` documents the environment variables this server reads; copy it to `.env` if
  51. you need to override `LOG_LEVEL`. `DATA_PROVIDER=mock` is the only implemented backend today.
  52. ## Architecture
  53. ```
  54. src/
  55. ├── index.ts, server.ts # stdio transport bootstrap, McpServer wiring
  56. ├── config/, logging/, errors/ # env config, stderr-only structured logging, safe error mapping
  57. ├── domain/ # types/enums shaped like real SAP B1 Service Layer entities
  58. ├── data/ # DataProvider interface + mock implementation (the backend swap seam)
  59. ├── matching/ # shared fuzzy-matching logic (customers + items)
  60. ├── tools/ # the 5 MCP tools
  61. ```
  62. Protocol wiring, business logic, domain modeling, and data access are kept in separate layers
  63. so that wiring up a real SAP Business One Service Layer backend later only touches
  64. `src/data/sap-service-layer/` plus a config flag — nothing in `src/tools/` or `src/domain/`
  65. needs to change.
  66. ### Tools
  67. | Tool | Purpose |
  68. |---|---|
  69. | `find_business_partner` | Fuzzy name search for a customer/vendor; returns ranked candidates, never a hard "not found" on a near-miss. |
  70. | `get_recent_sales_orders` | A customer's recent sales orders by `CardCode`. |
  71. | `get_open_overdue_invoices` | A customer's open/overdue AR invoices, with balance due and days overdue. |
  72. | `check_item_availability` | Fuzzy item lookup with on-hand/committed/available stock. |
  73. | `get_followup_suggestions` | Deterministic, rule-based visit talking points (overdue invoices → high, open orders → medium, reorder opportunities → low). |
  74. ## Security notes
  75. - No credentials are hardcoded anywhere; env-var config (`src/config/env.ts`) reserves
  76. `SAP_SERVICE_LAYER_URL` / `SAP_COMPANY_DB` / `SAP_USERNAME` / `SAP_PASSWORD` for a future
  77. real backend, unused while `DATA_PROVIDER=mock`.
  78. - When a real SAP Business One connection is wired up, use a dedicated, least-privilege,
  79. read-only integration user scoped to only the entities this server needs.
  80. - Future OData filter construction must escape user-provided strings (see the
  81. `sap-service-layer/README.md` notes) to avoid filter injection.
  82. - `npm audit` currently flags advisories against `vitest`/`vite`/`esbuild`'s dev-server chain
  83. (dev-only tooling, never exposed to a network here) and against the zod 4.x line generally;
  84. this project resolves to zod 3.25.x, which the advisory does not affect. Re-check
  85. `npm audit` before upgrading either.
  86. ## Out of scope (Phase 2 / future work)
  87. - Real SAP Business One Service Layer integration.
  88. - Remote/hosted MCP transport with OAuth, for a mobile + CarPlay replication of the original
  89. demo.
  90. - Write/mutation tools (this phase is deliberately read-only).
  91. - A "prompt library" feature (the original article mentions saving a reusable prompt for this
  92. scenario).
  93. - Multi-tenant/multi-company support, caching, pagination beyond simple `limit` params,
  94. telemetry.
  95. ## CI
  96. The CI workflow lives at [`docs/ci.yml.example`](docs/ci.yml.example) rather than
  97. `.github/workflows/ci.yml` — it was moved out of `.github/workflows/` only because the GitHub
  98. token used to push this repo didn't have the `workflow` scope needed to push a workflow file.
  99. To enable it: `gh auth refresh -h github.com -s workflow`, then
  100. `git mv docs/ci.yml.example .github/workflows/ci.yml` and push.
  101. ## License
  102. MIT — see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.