For food and meat processors running CSB-System
A CSB-System MCP server gives Claude, ChatGPT or Copilot read-first tools for customer orders, sales figures, products and batch tracing. CSB offers REST APIs and web services delivered per project, without a public reference. CSB ships no MCP server as of 21 September 2026; its own Agent Platform and Cesy work inside CSB.
Why CSB-System is hard for agents
01 · Docs
CSB publishes no API reference. REST APIs and web services are delivered per project, so the objects an agent can reach are scoped with CSB or your own CSB team. Every backend below is confirmed in the blueprint.
02 · Vendor AI
Cesy and the CSB Agent Platform cover chat questions and order entry inside CSB. An external connector has to earn its place: users in Claude or Copilot, or questions that cross into another system. The blueprint checks the overlap first.
03 · Traceability
Food and meat processing data is built around lot tracing, quality grading and catch weights. An answer on where a raw material batch went has to come from the traceability records, not a summary, and must say which record it read.
04 · Shop floor
CSB couples deeply with scales, machines and vision systems. Some figures sit in that hardware layer rather than in ERP tables. The blueprint names the source for each question before a tool is built.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | Integration of third-party systems (REST APIs, web services, communication modules, docs not published): exchange started by CSB or by the external system, centrally controlled and monitored; no public endpoint list · Data Interchange (EDI) (file/EDI, docs not published): incoming and outgoing messages are allocated to business transactions for customers, suppliers, logistics providers and trading systems |
| Authentication | Not documented publicly. How the REST APIs and web services authenticate is confirmed with CSB in the blueprint. |
| Vendor MCP server | No vendor server. No CSB MCP server; the CSB Agent Platform, launched on 12 August 2026, embeds agent flows in the CSB-System through controlled interfaces, with no mention of MCP. |
| Vendor AI assistant | Cesy, CSB's AI assistant, answers ad-hoc questions on sales, customers and products by chat; the CSB Agent Platform runs no-code agent flows such as order entry from email, PDF, Excel or voice, with a person in the loop. |
| Other connectors | None found. |
CSB-System SE (DE). Process-industry companies, above all food, beverage and meat processors, plus trade and logistics, chemicals, pharma and cosmetics; CSB states customers in 50 countries but publishes no customer count.
What we build
CSB-System SE does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# csb-system-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_customer_orders: # customer, delivery date -> orders and status
backend: confirmed in blueprint
mode: read
get_sales_figures: # customer or product group, period -> sales
backend: confirmed in blueprint
mode: read
trace_batch: # batch number -> upstream lots and downstream deliveries
backend: confirmed in blueprint
mode: read
get_product: # article number -> master data and specifications
backend: confirmed in blueprint
mode: read
draft_sales_order: # customer email or PDF content -> order draft a person confirms
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the CSB-System responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
CSB-System holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the goal is order entry from email or chat questions inside CSB, the CSB Agent Platform and Cesy are the shorter path and CSB maintains them. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine CSB with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your CSB-System owners and checks every backend against your release and licence. Week two tests whether a person's own CSB-System permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named CSB-System administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not as of 21 September 2026. CSB launched its own Agent Platform on 12 August 2026 and offers the Cesy assistant, both without MCP. An assistant outside CSB has to be connected through CSB's REST APIs or web services.
It needs REST API or web service access to your CSB installation, which CSB delivers per project. Which modules and licences that requires is not public, so check with CSB; we confirm it in the blueprint.
No. The connector is designed so each call runs as the asking person and CSB's own rights decide the answer. How the interfaces carry that identity is not documented publicly, so the blueprint tests it with two users before any build.
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your CSB-System administrator in the room if you like.