oracleservicecloud_get_tablesLABSCO SUMMARY
Support data you can ask about, without a report request.
The questions that come up about a service desk — how many tickets of this kind are open, which accounts keep coming back — are usually a report someone else builds. Exposed as SQL tables they become a conversation. This build has no write path: three tools, all read. If you need to create or update records, CData's separate MCP server product covers that; here the absence is the safety property.
What it is
A local, read-only MCP server from CData for Oracle Service Cloud. The CData JDBC driver presents the service data as relational tables; this server wraps the driver so an assistant can discover tables, read columns, and run SELECT queries against live records — the natural-language question goes in, the SQL is composed for you.
What you get
- The tables available in Oracle Service Cloud, as CSV with a header row —
get_tables - The columns on a table, so a query is written against the real schema —
get_columns - A SQL SELECT run against live data —
run_query - A prefix on the tool names taken from your
.prpfile, so multiple CData servers coexist in one client config - A
Tablessetting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with
Requirements
A licensed CData JDBC Driver for Oracle Service Cloud, installed and licensed separately, plus Java. Build from a clone with mvn clean install to get CDataMCP-jar-with-dependencies.jar. The .prp file carries the prefix, server name and version, driver path, driver class, the JDBC connection string produced by the driver's Connection String utility, and the optional table list; sources using OAuth authenticate in a browser during that step. Transport is stdio — the server runs on the same machine as the client.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
01
Getting an answer without filing a report request
Ask the question in plain language and let the assistant find the tables and compose the query.
02
Understanding an unfamiliar schema
List the tables and read the columns before you build anything that depends on their shape.
03
Letting an assistant near production support data
Use this read-only build so the connection cannot modify tickets or accounts, only read them.
04
Scoping what the assistant can see
List the permitted tables in the .prp file rather than leaving every table reachable.
3 tools
Listed in project docs. Your client may show a different list.
oracleservicecloud_get_columnsoracleservicecloud_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. Tool names start with the Prefix set in the .prp file; with the sample Prefix=oracleservicecloud they are oracleservicecloud_get_tables, oracleservicecloud_get_columns and oracleservicecloud_run_query.
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then point your client at the binary. This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/cdatasoftware/oracle-service-cloud-mcp-server-by-cdata.git
cd oracle-service-cloud-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Oracle Service Cloud from https://www.cdata.com/drivers/oracleservicecloud/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.oracleservicecloud.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.oracleservicecloud.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create oracle-service-cloud.prp with:
FILE · oracle-service-cloud.prp
Prefix=oracleservicecloud
ServerName=CDataOracleServiceCloud
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.oracleservicecloud.OracleServiceCloudDriver
JdbcUrl=<YOUR_JDBC_URL>
Tables=Tables only picks which tables also get a ready-made description for your assistant, and empty means none; the server can still list and query every table your connection string reaches, so to keep data out of reach, limit that connection or the account it signs in with.
Add the mcpServers entry (block below) to claude_desktop_config.json, then fully quit and re-open the client
MCP Clients
Claude Desktop — Windows, macOS / Linux
JSON
{
"mcpServers": {
"oracle-service-cloud": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_ORACLE_SERVICE_CLOUD>"
]
}
}
}