sage-200 -by-cdata

This MCP server provides a read-only interface to Sage 200 data via the CData JDBC driver. It wraps the JDBC driver in a lightweight MCP layer so large language models can query live Sage 200 data using natural language without directly writing SQL. The server is started by running the JAR with a .prp configuration file that contains the connection details to your Sage 200 data source. Tools exposed by the server include a get_tables helper to list available tables, a get_columns helper to list columns of a table, and a run_query helper to execute SQL queries. Clients typically interact through an MCP client (such as Claude Desktop) which can discover the server and invoke these tools through JSON-RPC payloads. For example, you can ask questions like which opportunities exist by industry, or query counts of open tickets, and the MCP server translates those requests into appropriate read-only SQL against Sage 200 data via the JDBC driver.

Prerequisites: Java Runtime Environment (JRE) or JDK installed, and Maven if you want to build the JAR locally. You will also need the CData JDBC Driver for Sage 200 and a valid license.

Step-by-step:

1. Clone the repository and navigate to it: "git clone https://github.com/cdatasoftware/sage-200-mcp-server-by-cdata.git" "cd sage-200-mcp-server-by-cdata"

2. Build the MCP JAR with dependencies: "mvn clean install" This creates CDataMCP-jar-with-dependencies.jar in the build output.

3. Download and install the CData JDBC Driver for Sage 200 from: https://www.cdata.com/drivers/sage200/download/jdbc

4. License the JDBC Driver (example steps):

• Locate the CData JDBC Driver installation and navigate to the lib folder.
• Run: java -jar cdata.jdbc.sage200.jar --license
• Enter your name, email, and a TRIAL license or your licensed key.

5. Create a Sage 200 .prp file with your JDBC connection details, for example sage-200.prp, using the required properties (Prefix, ServerName, ServerVersion, DriverPath, DriverClass, JdbcUrl, Tables).

6. Run the MCP server with the generated .prp file: java -jar CDataMCP-jar-with-dependencies.jar /PATH/TO/sage-200.prp

Note: The server uses standard I/O for communication, so it must be run on the same machine as the client when used locally.

Tips and notes:

• The MCP server operates in read-only mode by default for this Sage 200 example. To enable broader capabilities, ensure the underlying driver and server configuration align with your data source permissions.
• If Claude Desktop or another client cannot see the MCP server, fully quit and restart the client after starting the MCP server, or re-import the configuration.
• Ensure the JDBC Driver license is valid before starting the server; otherwise, connections may fail at runtime.
• The provided example configuration uses a placeholder path (/PATH/TO/sage-200.prp). Replace it with the actual absolute path to your prp file.
• Since the server uses stdio, the MCP server and client must run on the same machine or adapt the deployment to your environment if needed.