home / mcp / sap business one mcp server
This read-only MCP Server allows you to connect to SAP Business One data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
Configuration
View docs{
"mcpServers": {
"cdatasoftware-sap-business-one-mcp-server-by-cdata": {
"command": "java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/sap-business-one.prp"
]
}
}
}You have a local, read-only MCP Server that exposes SAP Business One data through the CData JDBC Driver. This server lets you ask natural language questions and receive live data answers without writing SQL. It’s designed for use with MCP clients that can run locally on the same machine as the server, providing a simple way to query SAP Business One data in real time.
After you start the MCP Server, connect your MCP client to the running server to ask questions about SAP Business One data. You’ll use the built-in tools to read data, including listing available tables, inspecting columns, and running queries. Typical usage patterns involve querying for counts, filtering results, and joining information across related tables to answer business questions such as revenue by account, open tickets, or calendar events.
Prerequisites you need before starting the MCP Server are: a Java Runtime Environment (JRE) and the ability to run Java from the command line. You will also build and run a Java JAR that hosts the MCP interface.
Step by step commands you will use: 1. Build the MCP server package 2. Install the CData JDBC Driver for SAP Business One 3. Create a .prp connection profile 4. Run the MCP server using the Java JAR and the .prp file
git clone https://github.com/cdatasoftware/sap-business-one-mcp-server-by-cdata.git
cd sap-business-one-mcp-server-by-cdata
mvn clean install
# After building, you will have the MCP JAR ready to run with a .prp file
# Ensure the CData JDBC Driver for SAP Business One is installed and licensedThe server is designed to run locally and use stdio for communication. This means you start the server process on the same machine as your MCP client, and the client communicates with it via standard input/output.
To connect to the SAP Business One data source, you create a JDBC connection profile that specifies the driver, connection string, and any required authentication. The profile is saved as a .prp file and passed to the MCP server when starting it.
You will typically expose a server named sapbusinessone and use a command line that starts the MCP JAR with your .prp file. The server then accepts queries via the MCP client’s normal workflow.
If the MCP Server does not appear in your MCP client, ensure you have fully restarted the client after starting the server. If the client cannot read data, verify that your connection string is correct and that the JDBC Driver is licensed and accessible from the server process.
If you encounter issues connecting to SAP Business One, double-check the connection string used in the .prp file and make sure OAuth or other authentication flows are completed as required by your source configuration.
For broader help, consider reaching out to the CData Support Team or community forums for guidance on MCP usage and SAP Business One connectivity.
This MCP server is distributed under the MIT License. You can use, modify, and share the software in compliance with the MIT terms.
Retrieves a list of tables available in the SAP Business One data source. The output is CSV with the first line as column headers.
Retrieves a list of columns for a specified table. The output is CSV with the first line as column headers.
Executes a SQL SELECT query against the SAP Business One data source and returns results.