14 Sep

Model Context Protocol (MCP)


E-invoicing in Germany: How to implement the obligation with SAP Business One

The Model Context Protocol (MCP) is an open standard that allows AI assistants and language models to access external data sources and tools. Anthropic released MCP in November 2024 and made it available as an open-source project. The standard regulates how a language model sends a request to a database, a file system or an enterprise system and receives the response back in a structured format. This means a language model no longer needs to be specially customised for every single data source.

The architecture follows a client-server model. An MCP server provides data or functions, such as access to a CRM, a calendar or a database. An MCP client, embedded in an AI application, connects to this server and retrieves the provided functions. Before MCP, a separate connection had to be programmed for every combination of AI application and data source. MCP replaces this multitude of individual solutions with a common protocol, much like a USB socket serves different devices via the same connection.

MCP in the SAP Business One context

For SAP Business One, MCP is relevant as soon as an AI assistant needs to access live business data, such as open items, item stock levels or document data via the Service Layer or the DI-API. Instead of building a separate interface for each type of request, an MCP server provides the relevant B1 functions once. Any MCP-enabled client, whether a chat interface or developer tool, can access it.

Demarcation

MCP is not a replacement for the service layer or a REST API. It sits rather as a layer above that: MCP standardises how an AI model calls such interfaces, not how the interface itself is built. Compared to retrieval-augmented generation, MCP covers a different need. RAG retrieves text knowledge from a knowledge base, whereas MCP gives the model access to structured data and executable functions.


 

Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: The reality behind the AI hype — and what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Generative AI in ERP

AI in ERP – but under control: What Versino AI means for SAP Business One users

AI can do a lot today – but without control, it often creates more problems than it solves. Versino AI connects AI models...
Wird geladen …