jiraservicemanagement_get_tablesLABSCO SUMMARY
Read-only by construction.
Three tools and no write path is the whole design: the model discovers tables, reads columns and runs SELECTs, so a badly framed question produces a wrong answer rather than a changed record. Two things decide whether it fits. The CData JDBC driver is a separate licensed product, with a trial key to start on. And the assistant can query every table the connection can see — the Tables field in the connection profile does not narrow that, so limit the connection or the account it signs in with.
What it is
A read-only MCP server built on CData's JDBC Driver for Jira Service Management. The driver exposes Jira Service Management as relational tables; the server puts three tools over it, so a client can discover what tables exist, read a table's columns, and run a SELECT — without anyone writing SQL by hand.
What you get
- The tables the driver exposes for Jira Service Management, returned as CSV with a header row —
jiraservicemanagement_get_tables - The columns of one of those tables, also as CSV, so a query can be composed against real field names —
jiraservicemanagement_get_columns - A SQL SELECT executed against live Jira Service Management data —
jiraservicemanagement_run_query - Tool names that carry the prefix you set in the connection profile — the sample uses
Prefix=jiraservicemanagement— so several CData servers can run side by side without colliding - 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
Java and Maven to build — mvn clean install produces CDataMCP-jar-with-dependencies.jar. The CData JDBC Driver for Jira Service Management is a separate download and needs licensing: run java -jar cdata.jdbc.jiraservicemanagement.jar --license and enter a name, an email and either TRIAL or a licence key. Connection settings go in a .prp file carrying Prefix, ServerName (the sample uses CDataJiraServiceManagement), ServerVersion, DriverPath, DriverClass (cdata.jdbc.jiraservicemanagement.JiraServiceManagementDriver), the JdbcUrl produced by the driver's connection-string utility, and the optional Tables list. The client then launches java -jar CDataMCP-jar-with-dependencies.jar jira-service-management.prp. Transport is stdio, so the server has to run on the same machine as the client. If the data source authenticates over OAuth, you approve it in a browser while building the connection string.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
01
Answering questions about ticket volume and backlog
Requests, queues and SLA fields arrive as tables, so 'how many open tickets in this project' becomes one SELECT.
02
Reporting across service projects
Query several projects in a single statement rather than exporting each queue separately.
03
Seeing which request fields are reportable
List the tables the driver models and read one table's columns before designing a report.
04
Narrowing what an assistant can read
Name the tables in the connection profile so only the request data you intend to expose is visible.
3 tools
Listed in project docs. Your client may show a different list.
jiraservicemanagement_get_columnsjiraservicemanagement_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 in the .prp file, so the README's Prefix=jiraservicemanagement gives jiraservicemanagement_get_tables, jiraservicemanagement_get_columns and jiraservicemanagement_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/jira-service-management-mcp-server-by-cdata.git
cd jira-service-management-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Jira Service Management from https://www.cdata.com/drivers/jiraservicedesk/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.jiraservicemanagement.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.jiraservicemanagement.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create jira-service-management.prp with:
FILE · jira-service-management.prp
Prefix=jiraservicemanagement
ServerName=CDataJiraServiceManagement
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.jiraservicemanagement.JiraServiceManagementDriver
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": {
"jira-service-management": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_JIRA_SERVICE_MANAGEMENT>"
]
}
}
}