veeva-mcp-server-by-cdata
Provides a local, read-only MCP server that wraps the CData JDBC Driver for Veeva so an MCP client (e.g., Claude Desktop) can list tables/columns and run SQL SELECT queries via simple MCP tool calls using JSON-RPC over stdio on the same machine.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture is largely delegated to the underlying CData JDBC driver and to how credentials are stored in the .prp file (not detailed here). The MCP server is local-only via stdio, reducing network exposure, but there is no evidence of fine-grained tool-level authorization, row-level filtering controls, or explicit secret-handling/log redaction guidance in the provided README. TLS is not directly applicable to stdio transport; JDBC connection security depends on the JDBC driver configuration.
⚡ Reliability
Best When
You want local interactive querying of Veeva data from an MCP client, with the user providing JDBC/driver configuration and credentials on the same host.
Avoid When
You need fine-grained access controls, auditability, or robust multi-user security guarantees for remote usage; or you require guaranteed pagination/streaming for large result sets.
Use Cases
- • Enable Claude/Desktop (MCP) users to query live Veeva data without writing SQL
- • Discover available Veeva tables and columns via tools
- • Run SELECT queries (read-only) through an MCP tool interface for analyst/research workflows
Not For
- • Use as a network-exposed service (stdio only, same-machine clients)
- • Writing/updating/deleting data (described as read-only)
- • Cases requiring a hosted/remote MCP endpoint or load-balanced availability
Interface
Authentication
The MCP server itself appears to rely on the JDBC driver configuration in the .prp file; README notes OAuth may require browser authentication when building the JDBC connection string.
Pricing
Pricing for the CData JDBC driver and/or managed MCP offering is not specified in the README content provided; server is distributed under MIT but driver licensing is required.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio and can only be used by clients running on the same machine
- ⚠ Tooling exposes run_query with SQL; agents should avoid overly broad SELECTs that could return very large result sets
- ⚠ Read-only nature: some agents may attempt write-style operations that the server/tooling may not support
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for veeva-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.