CData SAP Netweaver Gateway

What it is

A local MCP server wrapping the CData JDBC Driver for SAP Netweaver Gateway, which exposes the gateway's services as relational SQL models. The model is handed table discovery, column discovery, and one read-only query tool. Transport is stdio, so client and server run on the same machine.

What you get

• The tables the driver exposes through the gateway, returned as CSV with a header row — sapgateway_get_tables
• The columns of a chosen table, so queries reference real field names — sapgateway_get_columns
• A SQL SELECT executed against live SAP data — sapgateway_run_query
• A Tables setting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with

Requirements

Access to an SAP Netweaver Gateway plus a licensed CData JDBC Driver for SAP Netweaver Gateway — a trial licence is accepted via java -jar cdata.jdbc.sapgateway.jar --license. Java to run the server, Maven to build it (mvn clean install yields CDataMCP-jar-with-dependencies.jar). The .prp connection file supplies DriverClass as cdata.jdbc.sapgateway.SAPGatewayDriver, the driver jar path, a tool Prefix such as sapgateway, and the JDBC connection string from the driver's Connection String utility — OAuth-backed sources authenticate in a browser at that step. MIT licensed.

Setup effort

Build from source — git clone https://github.com/cdatasoftware/sap-netweaver-gateway-mcp-server-by-cdata.git

Tools you get

3 tools named in the project's documentation. Tool names take the Prefix from your .prp file, so with the README's Prefix=sapgateway they are sapgateway_get_tables, sapgateway_get_columns and sapgateway_run_query. All three only read (run_query executes SELECT only); read-write access needs CData's separate MCP Server for SAP Netweaver Gateway.

Where it runs

The documented client runs the server on your machine.