veeva-mcp-server-by-cdata

What is veeva-mcp-server-by-cdata?

veeva-mcp-server-by-cdata is a read-only Model Context Protocol (MCP) server built by CData that allows large language models (LLMs) like Claude Desktop to query live data from Veeva using natural language questions. It wraps the CData JDBC Driver for Veeva and exposes Veeva data as relational SQL models through a simple MCP interface.

How to use veeva-mcp-server-by-cdata?

Clone the repository, build with mvn clean install, install and license the CData JDBC Driver for Veeva, configure the connection string using the driver’s utility, create a .prp file with JDBC properties, then add the server to your Claude Desktop configuration by editing claude_desktop_config.json. Run or refresh Claude Desktop to start querying Veeva data.

Key features of veeva-mcp-server-by-cdata

• Read-only MCP server for Veeva data via natural language
• Uses CData JDBC Driver for Veeva as the underlying connector
• Exposes tools: get_tables, get_columns, and run_query (SELECT only)
• No SQL required – LLMs can ask questions directly
• Runs locally using stdio transport

Use cases of veeva-mcp-server-by-cdata

• Query Veeva data from Claude Desktop without writing SQL
• Answer business questions about Veeva records (e.g., “What is the correlation between closed won opportunities and account industry?”)
• Retrieve table and column metadata from Veeva for exploration

FAQ from veeva-mcp-server-by-cdata

What does this read-only server do vs the beta CData MCP Server?

This server is read-only. For full read, write, update, delete, and action capabilities, CData offers a separate free MCP Server for Veeva (beta) with simplified setup.

What dependencies or runtime are required?

Java (to run the JAR), the CData JDBC Driver for Veeva (must be downloaded and licensed), and Maven (for building the project). The server uses stdio and runs on the same machine as the client.

Where does my data live?

Data remains in Veeva. The server connects live to Veeva via the JDBC driver; no data is stored locally.

What are the known limits of veeva-mcp-server-by-cdata?

The server is read-only – only SELECT queries are supported. It uses stdio transport so the client must run on the same machine as the server.

How is authentication handled?

The JDBC driver handles OAuth authentication during connection string configuration. You authenticate in your browser when testing the connection.