Sage 200

This read-only MCP Server allows you to connect to Sage 200 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/).

java

GitHub Stars

java

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "cdatasoftware-sage-200-mcp-server-by-cdata": {
      "command": "java",
      "args": [
        "-jar",
        "/PATH/TO/CDataMCP-jar-with-dependencies.jar",
        "/PATH/TO/sage-200.prp"
      ]
    }
  }
}

You can query live Sage 200 data through a lightweight, read-only MCP server that exposes Sage 200 data via a simple MCP interface. This lets you ask natural-language questions and get up-to-date results without writing SQL, using the CData JDBC Driver to connect Sage 200 as relational data.

How to use

Once the MCP server is running, you connect your AI client (such as Claude Desktop) to the local MCP endpoint. You will be able to ask questions like “What is the open opportunities by account industry?” or “How many open tickets do I have in the SUPPORT project?” The server exposes tools to list tables and columns and to run read-only queries, returning results in a structured format that the AI client can interpret.

How to install

Prerequisites: Java Runtime Environment (JRE) 8+ and a Java-compatible environment. You will also need the CData JDBC Driver for Sage 200 and a Sage 200 data source configured via JDBC.

Step 1: Clone the repository and navigate into it.

git clone https://github.com/cdatasoftware/sage-200-mcp-server-by-cdata.git
cd sage-200-mcp-server-by-cdata

Step 2: Build the server to produce the MCP JAR.

mvn clean install

Step 3: Install the CData JDBC Driver for Sage 200 and license it following the driver’s setup instructions. This creates the JDBC driver JAR you will reference in the MCP configuration.

Step 4: Create the Sage 200 MCP connection file (sage-200.prp) with the appropriate JDBC settings. The file should include your driver path, JDBC URL, and the class name of the Sage 200 driver.

Prefix=sage200
ServerName=CDataSage200
ServerVersion=1.0
DriverPath=PATH\\TO\\cdata.jdbc.sage200.jar
DriverClass=cdata.jdbc.sage200.Sage200Driver
JdbcUrl=jdbc:sage200:InitiateOAuth=GETANDREFRESH;
Tables=

Step 5: Run the MCP server locally using the prepared Sage 200 PRP file. The server will start in stdio mode and listen for local clients.

java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/sage-200.prp

Note: The server uses stdio, so you can only connect from clients running on the same machine.

## Additional configuration and notes

 Claude Desktop integration requires adding a local MCP server entry to the Claude configuration file. The entry should point to the MCP JAR and the Sage 200 PRP file, using the Java runtime to launch the server. Ensure Claude Desktop is restarted after adding or updating the MCP configuration so the new server appears in the client.

## Troubleshooting

If the MCP server does not appear in your client, fully quit the client and restart it. If data cannot be retrieved, verify the JDBC connection string and driver path, and ensure the PRP file is correctly referenced by the MCP command.

## Available tools

### sage200\_get\_tables

Retrieves a list of available tables from the Sage 200 data source. Output is CSV with column headers on the first line.

### sage200\_get\_columns

Retrieves a list of columns for a specified table. Output is CSV with column headers on the first line.

### sage200\_run\_query

Executes a SQL SELECT query against the Sage 200 data source and returns the results.

Built by

VeilStrat

AI signals for GTM teams