postgresql-mcp-server-by-cdata
Provides a local MCP (Model Context Protocol) server that exposes data from a PostgreSQL database via CData JDBC Driver as MCP tools, primarily for reading (tables/columns) and running SELECT queries over stdio to an MCP client like Claude Desktop. It is configured by building a JAR and providing a JDBC connection .prp file.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security controls are largely inherited from the CData JDBC Driver and the database connection. The README does not describe MCP-level access control, TLS requirements for the database connection, secrets storage hygiene, query validation/sanitization, or protection against prompt-driven expensive/broad SELECTs. Since it accepts SQL input for run_query, guardrails are important at the client/agent layer.
⚡ Reliability
Best When
You need local, read-oriented access from an MCP-capable desktop client to PostgreSQL data using existing CData JDBC connectivity.
Avoid When
You need remote/multi-tenant access, strong guardrails around what queries can be executed, or an HTTP/REST interface with standard operational tooling.
Use Cases
- • Letting an LLM query live PostgreSQL data via natural-language questions without writing SQL
- • Discovering available tables and columns in a connected PostgreSQL data source
- • Executing read-only analytical queries (SELECT) through an MCP client
Not For
- • Direct use as a networked API service (the server is stdio-only and local-machine bound)
- • Production-grade CRUD workflows as described (the local MCP server is explicitly read-only in this project)
- • Use cases requiring fine-grained query safety controls (tooling exposes arbitrary SELECT SQL input)
Interface
Authentication
Authentication is delegated to the underlying CData JDBC Driver configuration included in the .prp/JdbcUrl. README mentions OAuth may be required for some data sources, but no MCP-level OAuth/auth flow is described.
Pricing
No pricing for the MCP server itself is provided in the README; CData JDBC Driver licensing is required (the README includes a driver license step).
Agent Metadata
Known Gotchas
- ⚠ Server communicates via stdio; it can only be used with clients on the same machine
- ⚠ Tool outputs for tables/columns are returned in CSV format; agents may need to parse CSV carefully
- ⚠ The run_query tool accepts arbitrary SQL (even though the project is marketed read-only), so agents can generate expensive or broad queries unless the client/agent constrains it
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for postgresql-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.