Certinia MCP Server by CData
A read-only MCP server that allows LLMs to query live Certinia data. Powered by CData.
certinia-mcp-server-by-cdata
CData's Model Context Protocol (MCP) Server for Certinia
:heavy_exclamation_mark: This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Certinia (beta).
Purpose
We created this read-only MCP Server to allow LLMs (like Claude Desktop) to query live data Certinia supported by the CData JDBC Driver for Certinia.
CData JDBC Driver connects to Certinia by exposing them as relational SQL models.
This server wraps that driver and makes Certinia data available through a simple MCP interface, so LLMs can retrieve live information by asking natural language questions — no SQL required.
Setup Guide
- Clone the repository:
git clone https://github.com/cdatasoftware/certinia-mcp-server-by-cdata.git cd certinia-mcp-server-by-cdata
- Build the server:
This creates the JAR file: CDataMCP-jar-with-dependencies.jarmvn clean install
- Download and install the CData JDBC Driver for {source}: https://www.cdata.com/drivers/certinia/download/jdbc
- License the CData JDBC Driver:
- Navigate to the
lib
folder in the installation directory, typically:- (Windows)
C:\Program Files\CData\CData JDBC Driver for Certinia\
- (Mac/Linux)
/Applications/CData JDBC Driver for Certinia/
- (Windows)
- Run the command
java -jar cdata.jdbc.certinia.jar --license
- Enter your name, email, and "TRIAL" (or your license key).
- Navigate to the
- Configure your connection to the data source (Salesforce as an example):
-
Run the command
java -jar cdata.jdbc.certinia.jar
to open the Connection String utility. -
Configure the connection string and click "Test Connection"
Note: If the data sources uses OAuth, you will need to authenticate in your browser.
-
Once successful, copy the connection string for use later.
-
- Create a
.prp
file for your JDBC connection (e.g.certinia.prp
) using the following properties and format:- Prefix - a prefix to be used for the tools exposed
- ServerName - a name for your server
- ServerVersion - a version for your server
- DriverPath - the full path to the JAR file for your JDBC driver
- DriverClass - the name of the JDBC Driver Class (e.g. cdata.jdbc.certinia.CertiniaDriver)
- JdbcUrl - the JDBC connection string to use with the CData JDBC Driver to connect to your data (copied from above)
- Tables - leave blank to access all data, otherwise you can explicitly declare the tables you wish to create access for
Prefix=certinia ServerName=CDataCertinia ServerVersion=1.0 DriverPath=PATH\TO\cdata.jdbc.certinia.jar DriverClass=cdata.jdbc.certinia.CertiniaDriver JdbcUrl=jdbc:certinia:InitiateOAuth=GETANDREFRESH; Tables=
Using the Server with Claude Desktop
-
Create the config file for Claude Desktop ( claude_desktop_config.json) to add the new MCP server, using the format below. If the file already exists, add the entry to the
mcpServers
in the config file.Windows
{ "mcpServers": { "{classname_dash}": { "command": "PATH\\TO\\java.exe", "args": [ "-jar", "PATH\\TO\\CDataMCP-jar-with-dependencies.jar", "PATH\\TO\\certinia.prp" ] }, ... } }
Linux/Mac
{ "mcpServers": { "{classname_dash}": { "command": "/PATH/TO/java", "args": [ "-jar", "/PATH/TO/CDataMCP-jar-with-dependencies.jar", "/PATH/TO/certinia.prp" ] }, ... } }
If needed, copy the config file to the appropriate directory (Claude Desktop as the example). Windows
cp C:\PATH\TO\claude_desktop_config.json %APPDATA%\Claude\claude_desktop_config.json
Linux/Mac
cp /PATH/TO/claude_desktop_config.json /Users/{user}/Library/Application\ Support/Claude/claude_desktop_config.json'
-
Run or refresh your client (Claude Desktop).
Note: You may need to fully exit or quit your Claude Desktop client and re-open it for the MCP Servers to appear.
Running the Server
- Run the follow the command to run the MCP Server on its own
java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/Salesforce.prp
Note: The server uses
stdio
so can only be used with clients that run on the same machine as the server.
Usage Details
Once the MCP Server is configured, the AI client will be able to use the built-in tools to read, write, update, and delete the underlying data. In general, you do not need to call the tools explicitly. Simply ask the client to answer questions about the underlying data system. For example:
- "What is the correlation between my closed won opportunities and the account industry?"
- "How many open tickets do I have in the SUPPORT project?"
- "Can you tell me what calendar events I have today?"
The list of tools available and their descriptions follow:
Tools & Descriptions
In the definitions below, {servername}
refers to the name of the MCP Server in the config file (e.g. {classname_dash}
above).
{servername}_get_tables
- Retrieves a list of tables available in the data source. Use the{servername}_get_columns
tool to list available columns on a table. The output of the tool will be returned in CSV format, with the first line containing column headers.{servername}_get_columns
- Retrieves a list of columns for a table. Use the{servername}_get_tables
tool to get a list of available tables. The output of the tool will be returned in CSV format, with the first line containing column headers.{servername}_run_query
- Execute a SQL SELECT query
JSON-RPC Request Examples
If you are scripting out the requests sent to the MCP Server instead of using an AI Client (e.g. Claude), then you can refer to the JSON payload examples below – following the JSON-RPC 2.0 specification - when calling the available tools.
source_get_tables
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "source_get_tables",
"arguments": {}
}
}
source_get_columns
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "source_get_columns",
"arguments": {
"table": "Account"
}
}
}
source_run_query
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "source_run_query",
"arguments": {
"sql": "SELECT * FROM [Account] WHERE [IsDeleted] = true"
}
}
}
Troubleshooting
- If you cannot see your CData MCP Server in Claude Desktop, be sure that you have fully quit Claude Desktop (Windows: use the Task Manager, Mac: use the Activity Monitor)
- If Claude Desktop is unable to retrieve data, be sure that you have configured your connection properly. Use the Connection String builder to create the connection string (see above) and copy the connection string into the property (.prp) file.
- If you are having trouble connecting to your data source, contact the CData Support Team.
- If you are having trouble using the MCP server, or have any other feedback, join the CData Community.
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
All Supported Sources
Related Servers
Microsoft Access Database
Allows AI to interact with Microsoft Access databases, supporting data import and export via CSV files.
MariaDB / MySQL
Provides access to MariaDB and MySQL databases for querying and data manipulation.
NEPSE Stock Data MCP Server
Access comprehensive stock market data from the Nepal Stock Exchange (NEPSE) via the ShareBazaar API.
Redis MCP Server
An MCP server for interacting with Redis databases, enabling LLMs to access key-value stores.
BioMCP
Connects AI assistants to authoritative biomedical data sources like PubMed and ClinicalTrials.gov, enabling natural language queries.
Hive MCP Server
Enables AI assistants to interact with the Hive blockchain through the Model Context Protocol.
MotherDuck
Query and analyze data with MotherDuck and local DuckDB
ChromaDB MCP
An MCP server for vector storage and retrieval using ChromaDB.
PostgreSQL
An MCP server for interacting with a PostgreSQL database.
SQL-Transpiler MCP Tool
Transpile SQL queries between different dialects using the sqlglot library.