SAP B1 Briefing MCP Server
Provides read-only sales-prep tools over SAP Business One Service Layer-shaped customer data, including fuzzy business partner lookup, recent sales orders, open/overdue invoices, item stock availability, and rule-based follow-up suggestions. Currently uses mock SAP B1-style data rather than a live SAP connection.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SAP B1 Briefing MCP Server Get me a briefing on Acme Corp: recent orders, overdue invoices, follow-ups."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SAP B1 Briefing MCP Server
An MCP (Model Context Protocol) server that lets Claude answer sales-prep questions — recent orders, overdue invoices, stock availability, follow-up suggestions — about SAP Business One-style customer data, conversationally.
Inspired by Tom Cenens' LinkedIn article "From the Driver's Seat to SAP: A Real-World AI Demo", which paired Claude's voice mode with a commercial SAP Business One MCP connector ("Amista AI Data Enabler") for hands-free customer briefings from a car. This project is an original implementation — it does not use or copy that product — built directly against the shape of SAP Business One's own Service Layer data, with mock data standing in for a real system.
What this is (and isn't), today
Data: mock, in-memory data shaped like real SAP Business One Service Layer entities (
BusinessPartners,Orders,Invoices,Items), not a live SAP connection. Seesrc/data/sap-service-layer/README.mdfor what a real backend would need.Transport: local stdio only, for Claude Desktop. No remote hosting, no mobile/CarPlay replication of the original demo (that needs a hosted server with OAuth — a documented future phase, not built here).
Tools: read-only. No tool can modify SAP data.
Related MCP server: CSM Intelligence MCP Server
Setup
npm install
npm run buildAdd 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.)
Restart Claude Desktop, then see docs/demo-script.md for a scripted
walkthrough, including the "misspoken customer name" moment the original demo highlighted.
Development
npm run dev # run directly with tsx, no build step
npm test # vitest
npm run lint # eslint
npm run typecheck # tsc --noEmit
npm run format # prettier --write.env.example documents the environment variables this server reads; copy it to .env if
you need to override LOG_LEVEL. DATA_PROVIDER=mock is the only implemented backend today.
Architecture
src/
├── index.ts, server.ts # stdio transport bootstrap, McpServer wiring
├── config/, logging/, errors/ # env config, stderr-only structured logging, safe error mapping
├── domain/ # types/enums shaped like real SAP B1 Service Layer entities
├── data/ # DataProvider interface + mock implementation (the backend swap seam)
├── matching/ # shared fuzzy-matching logic (customers + items)
├── tools/ # the 5 MCP toolsProtocol wiring, business logic, domain modeling, and data access are kept in separate layers
so that wiring up a real SAP Business One Service Layer backend later only touches
src/data/sap-service-layer/ plus a config flag — nothing in src/tools/ or src/domain/
needs to change.
Tools
Tool | Purpose |
| Fuzzy name search for a customer/vendor; returns ranked candidates, never a hard "not found" on a near-miss. |
| A customer's recent sales orders by |
| A customer's open/overdue AR invoices, with balance due and days overdue. |
| Fuzzy item lookup with on-hand/committed/available stock. |
| Deterministic, rule-based visit talking points (overdue invoices → high, open orders → medium, reorder opportunities → low). |
Security notes
No credentials are hardcoded anywhere; env-var config (
src/config/env.ts) reservesSAP_SERVICE_LAYER_URL/SAP_COMPANY_DB/SAP_USERNAME/SAP_PASSWORDfor a future real backend, unused whileDATA_PROVIDER=mock.When a real SAP Business One connection is wired up, use a dedicated, least-privilege, read-only integration user scoped to only the entities this server needs.
Future OData filter construction must escape user-provided strings (see the
sap-service-layer/README.mdnotes) to avoid filter injection.npm auditcurrently flags advisories againstvitest/vite/esbuild's dev-server chain (dev-only tooling, never exposed to a network here) and against the zod 4.x line generally; this project resolves to zod 3.25.x, which the advisory does not affect. Re-checknpm auditbefore upgrading either.
Out of scope (Phase 2 / future work)
Real SAP Business One Service Layer integration.
Remote/hosted MCP transport with OAuth, for a mobile + CarPlay replication of the original demo.
Write/mutation tools (this phase is deliberately read-only).
A "prompt library" feature (the original article mentions saving a reusable prompt for this scenario).
Multi-tenant/multi-company support, caching, pagination beyond simple
limitparams, telemetry.
CI
The CI workflow lives at docs/ci.yml.example rather than
.github/workflows/ci.yml — it was moved out of .github/workflows/ only because the GitHub
token used to push this repo didn't have the workflow scope needed to push a workflow file.
To enable it: gh auth refresh -h github.com -s workflow, then
git mv docs/ci.yml.example .github/workflows/ci.yml and push.
License
MIT — see LICENSE.
Available Tools
5 toolscheck_item_availabilityB
Check stock/availability for a product by item code or name (supports fuzzy name search).
Inputs: itemQuery (required), limit.
find_business_partnerA
Search for a business partner (customer or vendor) by name, even if misspelled or only partially remembered. Returns ranked candidate matches rather than a single forced result — use this to disambiguate before calling other tools with a CardCode.
Inputs: query (required), limit, cardType.
get_followup_suggestionsA
Generate heuristic follow-up talking points for a customer visit: combines overdue invoices, open orders, and previously-ordered items. Intended for 'what should I follow up on' style questions.
Inputs: cardCode (required).
get_open_overdue_invoicesA
Get a customer's open and/or overdue AR invoices by CardCode, including balance due and days overdue.
Inputs: cardCode (required), onlyOverdue.
get_recent_sales_ordersA
Get a customer's most recent sales orders by CardCode. Call find_business_partner first if you only have a name.
Inputs: cardCode (required), limit, sinceDays.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a clearly distinct resource and action: business partner lookup, sales orders, AR invoices, item availability, and an aggregate follow-up generator. The only potential overlap is get_followup_suggestions, but its description explicitly frames it as a heuristic summary for 'what should I follow up on' questions, distinguishing it from the raw-data retrieval tools.
All five tools use consistent snake_case verb_noun naming (find_business_partner, get_recent_sales_orders, get_open_overdue_invoices, check_item_availability, get_followup_suggestions). The verb variations (find/get/check) are semantically meaningful rather than inconsistent.
Five tools is well-scoped for a customer-visit briefing server, with each tool earning its place by covering a distinct briefing input. There is no filler or redundancy.
The surface covers the core briefing workflow: identify the customer, pull recent orders, surface overdue invoices, check item stock, and synthesize follow-ups. Minor gaps exist around customer profile details (contacts, credit status) and order/invoice line-level detail, but these are workable around for the stated briefing purpose.
Maintenance
Related MCP Connectors
Solk CRM for Claude: accounts, pipeline, visits, quotes, orders and tickets with your permissions.
Armiqo Brain is a free, read-only remote MCP server (Streamable HTTP, no account required) that gives AI assistants a B2B account-management playbook. Tools: list_modules, get_module, consult_brain. Modules cover account plans, risk radar (churn signals and 48-hour actions), renewals and expansion, meeting and QBR prep, stakeholder mapping, client health scoring, tricky client situations, and short message templates. Works with Claude, ChatGPT and Cursor.
Your SMB workspace in Claude or ChatGPT: tasks, notes, sales and Michèle's memory, via OAuth.
Read and write Sage Intacct from Claude or ChatGPT. Write tools are flagged for approval.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceProvides structured, read-mostly access to small-business back-office data including customers, invoices, and account notes, allowing Claude to query overdue invoices, revenue summaries, and more.MIT
- FlicenseNot gradedqualityDmaintenanceExposes simulated Salesforce CRM data as MCP tools for Claude Desktop, enabling customer success managers to prioritize at-risk accounts, review opportunities, cases, and Gong notes via natural language.-
- FlicenseAqualityDmaintenanceEnables Claude Desktop to answer natural-language questions about customers by exposing search, profile, order history, status filter, and spend statistics tools backed by local mock data, with a single-file swap path to Oracle AI Agent Studio later.5-
- AlicenseAqualityCmaintenanceEnables Claude to answer questions about a small business's own data by providing predefined sales, customer, refund, and inventory tools, plus a guarded read-only SQL query tool with audit logging.6MIT