sap-business-one -by-cdata

This MCP server provides a read-only interface to SAP Business One data via the CData JDBC Driver. It wraps the JDBC driver and exposes an MCP API so language models and clients can query live SAP Business One data without writing SQL. The server runs a single JAR that reads a .prp configuration file containing the JDBC connection details, and presents tools for listing tables, listing columns, and running SELECT queries through JSON-RPC style calls. You’ll interact with it by configuring Claude Desktop (or other MCP clients) to point at the server jar and the .prp file, then issue tool calls like sap_business_one_get_tables, sap_business_one_get_columns, or sap_business_one_run_query to retrieve results in CSV or table formats supported by the client.

Prerequisites:

• Java (JDK) installed and in PATH
• Maven (optional for building, not required to run if you use the prebuilt JAR)
• SAP Business One CData JDBC Driver installed and licensed (as described in the README)

Installation steps:

1. Build the MCP server (optional if you have the prebuilt JAR):

   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
   

   This produces CDataMCP-jar-with-dependencies.jar.

2. Install and license the CData JDBC Driver for SAP Business One as described in the README (download the driver, license it, and configure the connection).

3. Create a .prp file with your JDBC connection details (sap-business-one.prp) using the supplied properties format:

   Prefix=sapbusinessone
   ServerName=CDataSAPBusinessOne
   ServerVersion=1.0
   DriverPath=PATH/TO/cdata.jdbc.sapbusinessone.jar
   DriverClass=cdata.jdbc.sapbusinessone.SAPBusinessOneDriver
   JdbcUrl=jdbc:sapbusinessone:InitiateOAuth=GETANDREFRESH;
   Tables=
   

4. Run the MCP server:

   java -jar CDataMCP-jar-with-dependencies.jar /PATH/TO/sap-business-one.prp
   

   Note: The server uses stdio and is intended to be used with clients running on the same machine.

5. Configure your MCP client (e.g., Claude Desktop) to load the server, pointing to the JAR and the sap-business-one.prp file as shown in the README examples.

Tips and caveats:

• The MCP server is read-only in this variant; for full read-write access, see the full MCP Server for SAP Business One option referenced in the README.
• The server communicates via stdio, so it must run on the same host as the client.
• Ensure the JDBC driver path in sap-business-one.prp points to the actual JAR file installed on the system.
• If the MCP server does not appear in Claude Desktop, fully quit and restart the client so it re-scans for servers.
• If you encounter connection issues, verify that the driver license has been applied and that the connection string (JdbcUrl) matches your SAP Business One environment.
• The available tools follow the naming convention {servername}_get_tables, {servername}_get_columns, and {servername}_run_query and return data in CSV format for columns and tables.