How cdatasoftware/cdata-jdbc-mcp-server works
Project type and purpose
• This is a standalone Java “read-only” MCP (Model Context Protocol) server.
• It wraps CData JDBC drivers to expose data from external sources via a simple tooling interface over stdio for LLM clients (e.g., Claude Desktop).
File structure
• pom.xml – Maven build file.
• src/main/java/com/cdata/mcp – core packages:
– Program.java: entry point, bootstraps the server.
– Config.java, Constants.java: configuration and static values.
– ITool.java, IResource.java: abstractions for “tools” (actions) and “resources.”
– CsvUtils/CsvWriter, JsonSchemaBuilder: formatting and schema generation.
– StringUtil, UrlUtil: utility classes.
– Table.java: domain model for tables.
• src/main/java/com/cdata/mcp/resources – HTTP‐like or MCP resources (e.g., TableMetadataResource).
• src/main/java/com/cdata/mcp/tools – concrete tools: GetTablesTool, GetColumnsTool, RunQueryTool.
• src/test – unit tests for JsonSchemaBuilder and Table.
README for additional insights
• Describes the overall architecture: MCP server communicates over stdio, uses a .prp file for configuration, loads a CData JDBC Driver, exposes three main tools to an LLM client.
• No web/API layer—communication is purely stdio-based.
• Workflow: load config -> instantiate driver -> register tools -> listen/serve tool invocations -> return CSV/JSON to client.
Detail
• Every package/component group.
• How tests fit in (unit testing layer not present at runtime, but ensures correctness of JsonSchemaBuilder and Table model).
• Don’t over-complicate—focus on drawing as many discrete components/modules as possible to highlight separation of concerns.