How to connect Claude to SAP Business One
Short answer
Claude reaches Business One through tools, most cleanly via a Model Context Protocol server that wraps the Service Layer. You can run Claude through Anthropic's API or through a cloud provider such as AWS Bedrock or Google Vertex AI, or put an open-weight model on your own hardware if data cannot leave.
Teams running Business One tend to have strong opinions about their data and little appetite for another dashboard. What they often want is to ask a capable assistant about stock, orders and vendors, and have it show its work. Claude suits that style because it handles long documents and tool use well, and because its tool protocol is open.
The practical question is where the glue lives. Claude does not know your Service Layer address or your company database. Something has to hold credentials, call the API, shape results and enforce permissions. That something is a small server you control.
Below is the architecture, the choices on hosting the model, and the points that matter for B1 specifically: licences, sessions, user-defined fields and the HANA versus SQL Server split.
What teams use it for
Ask about stock and orders in plain language
A planner asks which open sales orders are at risk next week. Claude calls availability and order tools and explains the answer with document numbers.
Vendor performance review
Claude reads goods receipt PO history against promised dates and summarises which vendors are slipping, with the supporting lines.
Month-end explanations
Accountants ask why inventory valuation or open AP moved. Claude reads the relevant read-only views and drafts an explanation to review.
Long contract and certificate reading
Upload a supply agreement or material certificate, extract terms and compare them with B1 vendor master and item data.
Customisation understanding
Developers paste a stored procedure used for transaction notification and ask Claude to explain its logic before changing it.
Query drafting for Query Manager
Claude drafts SQL for the B1 schema, which a power user tests on a copy before saving.
SAP Business One integration surface
- Service Layer: the REST/OData endpoint under /b1s/v1 with a session-cookie login. This is the natural backend for an MCP server's tools.
- SQLQueries and view-style entities: fixed, parameterised reads that keep Claude away from raw SQL. Support differs by version and patch.
- Read-only reporting database or HANA calculation views: a good source for analytic questions without loading the production server.
- Attachments2 and the attachments folder: documents users attach to business partners, items and documents, which Claude can read after the wrapper fetches them.
- Authorisations and approval templates: Claude's B1 user is subject to them, which is a feature, not a limitation.
- UDFs and UDTs: custom data that must be exposed deliberately in tool schemas.
How it works
- 1
Choose the hosting route for Claude
Options include Anthropic's API directly, or Claude via AWS Bedrock or Google Vertex AI if your organisation already has a cloud agreement and wants regional controls. Check which models and regions each currently offers.
- 2
Build or adopt an MCP server
Implement tools such as get_item_availability, get_sales_order, list_open_pos and get_vendor_history. Each calls the Service Layer and returns compact JSON.
- 3
Run it where the Service Layer lives
Use stdio for single-user desktop testing and an authenticated HTTP transport for team use. Keep the server inside your network and expose only what the client needs.
- 4
Scope the B1 user
Create a read-only user for the server and map each human to their own permissions where practical. Budget for the Service Layer licence usage.
- 5
Connect a client
Register the server in a Claude client that supports MCP, or call Claude through the API from an internal tool using the same tool definitions.
- 6
Add audit and limits
Log tool calls, cap rows returned, set timeouts, and review what people actually ask in the first weeks.
Example flows
At-risk order question
Trigger: A planner types, "Which orders due Friday cannot ship complete?"
- Claude calls the open sales orders tool filtered by due date.
- It calls availability for each short item across warehouses.
- It checks open purchase orders for incoming receipts before Friday.
- It replies with a table and notes where a PO could close the gap.
Result: The planner sees real document numbers and decides what to expedite.
Vendor certificate check
Trigger: Receiving staff upload a material certificate PDF.
- The wrapper retrieves the matching purchase order and item spec.
- Claude compares heat or lot, material grade and revision.
- It flags mismatches and lists what it could not read.
- A quality person confirms and attaches the result.
Result: Quicker receiving inspection with a record of what was compared.
Keeping data on-prem
For sites that cannot send Business One data to any hosted model, the same MCP server design works with an open-weight model served on your own GPUs through vLLM or Ollama, with a client that speaks the same tool protocol. The Service Layer, the MCP server and the model all sit in your network, and nothing crosses the perimeter. Expect to trade some reasoning strength and long-context quality for control, so test your real questions before committing. A hybrid is also common: Claude through a cloud provider for non-sensitive tasks, and a local model for pricing, drawings and customer data.
Security checklist
- Keep the MCP server inside your network and authenticate every client.
- Use read-only B1 credentials, stored in a secrets manager.
- Limit returned fields and rows; avoid sending cost or personal data unless needed.
- Review the data retention terms of whichever Claude hosting route you pick.
- Record who asked what and which documents were returned.
Ways to get it done
Existing connector or community MCP server for SAP
Effort: Low if suitable, otherwise wasted time.
Worth checking, but verify it supports the B1 Service Layer and not only S/4HANA or ECC before relying on it.
Build your own MCP server
Effort: One to four weeks for a read-only server.
Best control when you have a B1-aware developer and a defined list of questions.
Partner build including Netray
Effort: Scoped pilot, then iterate.
When you want the server, hosting choice and on-prem fallback designed together.
Pitfalls
- !Assuming an SAP connector built for S/4HANA works with the B1 Service Layer. Interfaces differ.
- !Giving Claude a powerful B1 login instead of a read-only user.
- !Returning huge result sets, which blow up context and cost.
- !Not testing after B1 version upgrades that change Service Layer behaviour.
- !Ignoring UDFs, so answers miss fields the business relies on.
Frequently asked questions
Does Claude have a native SAP Business One connector?
Do not assume so. Claude uses tools exposed over MCP or its API, and the B1 piece is usually a small server you or a partner build over the Service Layer. Check current connector listings, but verify any SAP connector actually targets Business One.
Which is better, Anthropic's API, Bedrock or Vertex AI?
It depends on your procurement, region and compliance needs. Bedrock and Vertex suit firms already committed to AWS or Google Cloud and wanting their existing controls. The direct API may get new features first. Compare current model availability and data terms before choosing.
Can Claude update records in Business One?
Only if you build write tools. The safer pattern is read-only first, then draft documents that a user approves. Keep approval procedures active and log every proposed change so reviewers can see what the model intended.
Can I use Claude if the data must stay on-prem?
Claude itself is hosted by Anthropic or a cloud provider, so strict on-prem needs call for an open-weight model behind the same tool layer. Many firms use both, routing sensitive questions locally and general tasks to a hosted model.
Will it slow down my B1 server?
Light read tools rarely matter, but unbounded queries can. Use paging, row limits and, for analytics, a reporting copy of the database. Run heavier jobs outside peak hours and watch Service Layer load after launch.
Want Claude working on your SAP Business One?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment