xml-documents-mcp-server-by-cdata
Provides a read-only MCP server that exposes XML Documents data (via CData JDBC Driver for XML Documents) as MCP tools for listing tables/columns and running SELECT queries. Intended for local use with MCP clients like Claude Desktop via stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Likely relies on underlying CData JDBC driver for transport security and auth, but the MCP wrapper README does not describe TLS enforcement at the MCP layer, secret redaction, or tool-level authorization. JDBC connection details are provided via a local .prp file; avoid logging/embedding this file in prompts or shared logs. stdio local-only reduces exposure but does not provide built-in auth boundaries if multiple processes/users can access the host.
⚡ Reliability
Best When
You want an on-machine MCP tool for read-only exploration and querying of XML Documents data using an LLM client.
Avoid When
You need robust remote/API gateway style access, strong operational controls (auth per request, rate limiting), or write capabilities.
Use Cases
- • Query live XML-backed data without writing SQL (natural language questions)
- • Explore available tables and columns from the XML Documents data source
- • Perform read-only analytics using SQL SELECT via MCP tools
Not For
- • Production multi-tenant remote service exposure (no network server described; stdio local-only)
- • Write/update/delete operations (this specific project is read-only)
- • Use when you cannot run/build Java locally or cannot install the required CData JDBC driver
Interface
Authentication
The server itself is configured via a .prp file that includes a JDBC URL (e.g., may use InitiateOAuth=GETANDREFRESH). Scope/granularity and tool-level permissions are not described in the MCP server README.
Pricing
No pricing for this MCP wrapper is described; the underlying CData JDBC driver requires a license/trial.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio and can only be used with clients running on the same machine.
- ⚠ This project is explicitly read-only; attempts to use write semantics will fail (and tool set only lists read-oriented tools).
- ⚠ Tool outputs are CSV; agents should parse CSV carefully (first row contains headers).
- ⚠ Underlying JDBC driver configuration (.prp) and connection string are required; failures will likely originate from driver authentication/connectivity issues.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for xml-documents-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.