Cvent MCP Server by CData

What it is

A Java MCP server that puts CData's JDBC Driver for Cvent behind three read-only tools: list the tables, list a table's columns, and run a SQL SELECT. The driver is what does the work — it exposes Cvent as relational SQL models — and the server hands those models to your client so you can ask questions in plain language instead of writing SQL yourself.

What you get

• get_tables returns the tables available in the data source, as CSV with a header row
• get_columns returns the columns of one table, in the same CSV shape
• run_query executes a SQL SELECT and returns the rows
• Every tool name starts with the Prefix in your .prp file (cvent_ in the sample), so several CData servers can run side by side without colliding
• Ask in plain language — how many people registered for an event, say — and the client picks the tools and writes the SQL

Requirements

Build the server with mvn clean install, which produces CDataMCP-jar-with-dependencies.jar. Separately download the CData JDBC Driver for Cvent and license it: run java -jar cdata.jdbc.cvent.jar --license and enter your name, email and either TRIAL or a licence key. Then write a .prp file naming DriverClass=cdata.jdbc.cvent.CventDriver plus the JdbcUrl you build in the driver's connection-string utility, and point your client at java -jar with the jar and that file. Transport is stdio, so the server has to run on the same machine as the client.

Setup effort

Build from source — clone the repository, then point your client at the binary

Tools you get

3 tools named in the project's documentation. All tools are read-only; full read-write access is the separate paid CData MCP Server for Cvent. Tool names start with the Prefix in the .prp file (cvent_ in the sample), and Tables= in the .prp limits which data they reach.

Where it runs

The documented client runs the server on your machine.