hcl-domino-mcp-server-by-cdata
Provides a locally hosted MCP (Model Context Protocol) server that exposes HCL Domino data via CData JDBC Driver models. It is described as a read-only MCP server that lets LLM clients (e.g., Claude Desktop) discover tables/columns and run SQL SELECT queries through MCP tool calls over stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Transport security for MCP stdio is not applicable in the README, and no explicit TLS/network controls are described. Authentication/authorization appears to be entirely handled by the underlying CData JDBC Driver credentials configured locally; the README does not describe MCP-level scoping/least-privilege controls per tool call. The .prp file contains JDBC connection details (potentially including tokens/credentials); guidance on secure storage/avoiding logging is not provided. Dependency/CVE hygiene and build security details are not documented in the provided content.
⚡ Reliability
Best When
You need local, read-only access to Domino data from an MCP client on the same host, and you can supply JDBC driver credentials and a prepared .prp configuration.
Avoid When
You require network-accessible APIs, fine-grained authorization per query/user, or guaranteed guardrails to prevent excessive/unsafe queries (no such controls are described).
Use Cases
- • Ask natural-language questions over live HCL Domino data (read-only) using an MCP-capable client
- • Generate analytics by querying Domino records with SQL SELECT via an LLM
- • Schema discovery for Domino-backed models (list tables/columns) to support downstream querying
Not For
- • Direct use as a public network API (it uses stdio and is intended to run on the same machine as the MCP client)
- • Write/update/delete operations (project documentation emphasizes read-only for this server)
- • Production-grade multi-tenant services without additional sandboxing and access controls
Interface
Authentication
Authentication is delegated to the CData JDBC Driver and whatever it supports for the Domino backend. The README does not document MCP-level auth; it focuses on licensing the JDBC driver and configuring the connection string.
Pricing
Cost details are not provided for the MCP server repo. The README indicates use of the CData JDBC Driver, which typically requires licensing.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio; it can only be used by clients running on the same machine.
- ⚠ Need to correctly populate the .prp file (DriverPath, DriverClass, JdbcUrl, and optionally Tables).
- ⚠ Claude Desktop may require fully quitting and reopening to detect new MCP server entries.
- ⚠ Tool outputs for get_columns/get_tables are returned in CSV format; agents may need to parse CSV carefully.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for hcl-domino-mcp-server-by-cdata.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.