The gateway's services become tables, and the model's path is fixed: find the table, read its columns, then write one SELECT. That is a narrow surface, but narrow is the right shape for a system where a wrong write would matter — nothing here can write. The CData driver licence is the real prerequisite.
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.
- 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` property in the connection file limiting what is exposed at all; blank exposes everything
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.