Jira Service Management MCP Server by CData

@CDataSoftware

Basic information

About Jira Service Management MCP Server by CData

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 Jira Service Management (beta): https://www.cdata.com/download/download.aspx?sku=GKZK-V&type=beta

#jira #mcp-server #cdata

Jira Service Management MCP Server by CData config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\jira-service-management.prp"
      ]
    }
  }
}

Jira Service Management MCP Server by CData tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Jira Service Management MCP Server by CData?

This is a read-only MCP server that lets large language models (LLMs) like Claude Desktop query live Jira Service Management data using natural language. It wraps the CData JDBC Driver for Jira Service Management, exposing the underlying data as relational SQL tables through a simple MCP interface. It is intended for developers who need to retrieve ticket, project, and customer data without writing SQL.

How to use Jira Service Management MCP Server by CData?

Clone the repository, build the JAR with Maven (mvn clean install), install and license the CData JDBC Driver for Jira Service Management, then create a .prp configuration file with your JDBC connection string. Add the server to your Claude Desktop configuration (claude_desktop_config.json) using the java -jar command pointing to the JAR and the .prp file. After restarting Claude, you can ask natural‑language questions about your Jira Service Management data.

Key features of Jira Service Management MCP Server by CData

Read-only access to Jira Service Management data via natural language queries.
Exposes data as relational SQL tables through the CData JDBC Driver.
Three built‑in tools: get_tables, get_columns, and run_query.
Supports any LLM client that follows the MCP standard (stdio transport).
Uses OAuth-based authentication for secure connections (configurable in the JDBC connection string).

Use cases of Jira Service Management MCP Server by CData

Ask Claude Desktop “How many open tickets do I have in the SUPPORT project?”
Retrieve a list of all columns in the Customers table to understand available data.
Summarize recent service requests by querying the Requests table.
Get a count of tickets by priority without writing SQL manually.

Frequently asked questions

Is this server read‑only?

Yes. The project explicitly builds a read-only MCP server. For full CRUD and action capabilities, CData offers a separate MCP Server (beta) with a simplified setup.

What are the runtime requirements?

You need Java (to run the MCP server JAR), Apache Maven (to build the project), and a licensed copy of the CData JDBC Driver for Jira Service Management (trial or paid).

Where does the data live?

Data resides in your Jira Service Management instance (cloud or on‑premises). The JDBC driver connects to it directly; the MCP server does not store or cache data.

What transport and authentication are supported?

The server uses the `stdio` transport, so it runs on the same machine as the client. Authentication is handled via OAuth through the JDBC connection string (configured in the `.prp` file).