hcl-domino -by-cdata

The hcl-domino MCP server provides a local, read-only interface to data exposed by the CData JDBC Driver for HCL Domino. Once started, it serves live data to clients via the MCP (Model Context Protocol) tooling, enabling natural-language queries to be translated into SQL under the hood. Clients such as Claude Desktop can discover and interact with the server by using the built-in tools to list available tables, fetch column metadata, and run SQL queries against the Domino data source. The server is designed to run on the same machine as the client (stdio-based), so it’s well-suited for local experimentation and testing with LLMs that need up-to-date Domino data without exposing a remote endpoint.

The available tools follow a naming pattern based on the MCP server identifier (configured in your claude_desktop_config.json). You’ll typically see tools like hcl-domino_get_tables to retrieve accessible tables, hcl-domino_get_columns to list columns for a chosen table, and hcl-domino_run_query to execute a SELECT (or other SQL) statement. Outputs are delivered in CSV format for tables and columns, or as query results for run_query, making it easy to feed into downstream prompts or analyses.

Prerequisites:

• Java Runtime Environment (JRE) 8+ (preferably a recent JDK for building)
• Maven for building the MCP server
• Access to download the CData JDBC Driver for HCL Domino and a valid license

Installation steps:

1. Clone the repository and build the MCP server

   • git clone https://github.com/cdatasoftware/hcl-domino-mcp-server-by-cdata.git
   • cd hcl-domino-mcp-server-by-cdata
   • mvn clean install
   • This produces the JAR file: CDataMCP-jar-with-dependencies.jar (located in the target/ directory)

2. Install the CData JDBC Driver for HCL Domino

   • Download from: https://www.cdata.com/drivers/domino/download/jdbc
   • Install the driver on your system following the vendor’s instructions
   • License the driver via the steps described in the README (navigate to the lib folder and run the license command)

3. Prepare the MCP PRP configuration

   • Create a hcl-domino.prp file with your JDBC connection details (Prefix, ServerName, ServerVersion, DriverPath, DriverClass, JdbcUrl, Tables) as shown in the README

4. Run the MCP server locally

   • Example command (adjust paths to your environment): java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/hcl-domino.prp
   • The server runs over stdio and can be consumed by clients on the same machine

5. Integrate with Claude Desktop or other MCP clients

   • Update your claude_desktop_config.json with an entry referencing the Java invocation and the path to the generated hcl-domino.prp
   • Launch or refresh the client to see the new MCP server

Tips and common issues:

• The MCP server is read-only by design in this variant; for full read/write/delete capabilities, refer to the fully managed or different MCP server variants offered by CData.
• Ensure the hcl-domino.prp file correctly points to the JDBC Driver JAR and the JDBC URL; a misconfigured JdbcUrl will prevent the server from connecting to Domino.
• Because the server uses stdio for IPC, the client must run on the same host. If you need remote access, consider a different MCP deployment path or a tunnel-enabled setup.
• When licensing the driver, follow the exact steps in the README’s license section to avoid startup failures.
• If Claude Desktop cannot discover the server, fully quit and restart the client after updating claude_desktop_config.json and ensure the MCP server process is running.