Sage 200 By Cdata MCP Server

CData JDBC Driver connects to Sage 200 by exposing them as relational SQL models.

Remote serverstreamable-http

What is the Sage 200 By Cdata MCP server?

Most database access work still happens through a UI a human drives. Sage 200 By Cdata MCP server moves it into the conversation instead. CData JDBC Driver connects to Sage 200 by exposing them as relational SQL models.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • source_get_tables — The source_get_tables tool exposed by this server
  • source_get_columns — The source_get_columns tool exposed by this server
  • source_run_query — The source_run_query tool exposed by this server

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sage 200 By Cdata's toolset — source_get_tables, source_get_columns, source_run_query — is a fair guide to whether it matches your workflow. It is maintained by CDataSoftware; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Sage 200 By Cdata's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
source_get_tablesThe source_get_tables tool exposed by this server.
source_get_columnsThe source_get_columns tool exposed by this server.
source_run_queryThe source_run_query tool exposed by this server.

How to install the Sage 200 By Cdata MCP server

**Linux/Mac**
      ```json
      {
        "mcpServers": {
          "{classname_dash}": {
            "command": "/PATH/TO/java",
            "args": [
              "-jar",
              "/PATH/TO/CDataMCP-jar-with-dependencies.jar",
              "/PATH/TO/sage-200.prp"
            ]
          },
          ...
        }
      }

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Sage 200 By Cdata to source get tables.
  • Use Sage 200 By Cdata to source get columns.
  • Use Sage 200 By Cdata to source run query.

Frequently asked questions

It connects Sage 200 By Cdata to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (source_get_tables, source_get_columns, source_run_query) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Sage 200 By Cdata directly.