MCP Server for SAP Business One

If you have read that AI agents can now “use tools”, the Model Context Protocol is the standard that made it practical. This page explains what an MCP server for SAP Business One is, how a tool call actually flows, and what B1Nexus exposes.

The protocol in one paragraph

MCP defines how an AI application (the client) talks to an external system (the server). The server advertises a list of tools, each with a name, a description and a typed schema for its arguments. The client hands that list to the model. When the model decides a tool is needed, the client calls it, the server executes it, and the result returns as structured data the model can reason over.

The important consequence: the model does not need to know your ERP in advance. It reads what is available at connection time.

Why that matters for an ERP

• One integration, many clients. Assistants, IDEs and agent frameworks that speak MCP all work against the same server.
• Discovery instead of hard-coding. Expose a new tool and connected agents can use it without any change on their side.
• Typed arguments. The schema constrains what the model can send, which removes a whole class of malformed requests.
• A real boundary. What is not exposed as a tool is not reachable.

Anatomy of a call

A question like “which customers have overdue invoices?” resolves in four steps:

• The client sends the question plus the available tool list to the model.
• The model selects a tool and supplies arguments — for example an invoice query filtered to open, overdue documents.
• B1Nexus executes that against SAP Business One through the Service Layer.
• Rows return to the model, which composes the answer — with the underlying call visible.

Connecting a client

MCP servers are typically registered in the client's configuration. The shape is consistent across applications:

{
  "mcpServers": {
    "b1nexus": {
      "command": "b1nexus",
      "args": ["--company", "SBODEMO"],
      "env": {
        "B1_SERVICE_LAYER": "https://sap:50000/b1s/v1"
      }
    }
  }
}

Once connected, the client lists the tools B1Nexus offers and the model can begin using them.

What B1Nexus exposes

Rather than a thin wrapper over raw endpoints, B1Nexus exposes tools that match how people describe their work — querying business partners, sales, purchasing and items; retrieving a full customer or item picture in a single call; creating documents; taking approval decisions. A general query tool covers the 340+ objects available through the Service Layer for everything else.

The complete list is on the tools page. For the wider context, see SAP Business One AI integration.

Frequently asked questions

What is MCP?

The Model Context Protocol is an open standard for connecting AI applications to external systems. An MCP server exposes a set of tools; an MCP-capable client discovers those tools and lets the model call them with structured arguments.

Why not just build a custom integration?

You can, and for a single AI application it may be enough. The cost appears with the second and third application, and every time an interface changes. A protocol means one server serves all compliant clients.

Does B1Nexus run inside my network?

It connects to your SAP Business One environment, so it is deployed where that environment is reachable. Data stays in your ERP; the server calls it on demand rather than copying it elsewhere.

Related