EnterpriseDB MCP Server by CData
@CDataSoftware
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for EnterpriseDB (beta): https://www.cdata.com/download/download.aspx?sku=JEZK-V&type=beta
Overview
What is EnterpriseDB MCP Server by CData?
The EnterpriseDB MCP Server by CData is a read-only Model Context Protocol (MCP) server that lets LLMs like Claude Desktop query live EnterpriseDB data using natural language, without writing SQL. It wraps the CData JDBC Driver for EnterpriseDB, exposing EnterpriseDB tables as relational SQL models through a simple MCP interface.
How to use EnterpriseDB MCP Server by CData?
Clone the repository, build the JAR with mvn clean install, download and license the CData JDBC Driver for EnterpriseDB, create a .prp file with your JDBC connection string and driver details, then configure Claude Desktop (or another MCP client) to launch the server using the java -jar command referencing that .prp file. The server uses stdio transport and must run on the same machine as the client.
Key features of EnterpriseDB MCP Server by CData
- Read-only access to live EnterpriseDB data via MCP
- Wraps the CData JDBC Driver for EnterpriseDB
- Supports natural-language queries through LLM clients
- Exposes tools: get_tables, get_columns, run_query
- SQL SELECT queries returned in CSV format
- Requires Java runtime and Maven for build
Use cases of EnterpriseDB MCP Server by CData
- Letting Claude Desktop answer business questions from EnterpriseDB
- Exploring EnterpriseDB table structure without SQL knowledge
- Querying EnterpriseDB for read-only analytics and reporting
- Integrating EnterpriseDB data into AI-driven workflows
FAQ from EnterpriseDB MCP Server by CData
Is this server read-only?
Yes, the EnterpriseDB MCP Server by CData is explicitly read-only. For full read, write, update, and delete capabilities, CData offers a separate beta MCP Server for EnterpriseDB with simplified setup.
What runtime dependencies does it require?
You need Java (to run the JAR), Maven (to build the server), and the CData JDBC Driver for EnterpriseDB (installed and licensed separately).
Where does the data live?
The data stays in your EnterpriseDB instance. The server queries it live through the JDBC Driver; no data is copied or stored by the MCP server itself.
What transport does the server use?
The server uses stdio transport, so it must run on the same machine as the MCP client (e.g., Claude Desktop).
How is authentication handled?
Authentication is configured in the JDBC connection string within the .prp file. The JDBC Driver must be licensed (via a separate command or license key) before use.
