jira-mcp-server-by-cdata

Created By
CDataSoftwarea year ago
This read-only MCP Server allows you to connect to Jira data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at
Overview

What is jira-mcp-server-by-cdata?

The jira-mcp-server-by-cdata is a read-only Model Context Protocol (MCP) Server designed to connect to Jira data using CData JDBC Drivers, enabling LLMs like Claude Desktop to query live Jira data without needing SQL.

How to use jira-mcp-server-by-cdata?

To use the server, clone the repository, build it, install the CData JDBC Driver for Jira, configure your connection, and create a configuration file for Claude Desktop to add the MCP server.

Key features of jira-mcp-server-by-cdata?

  • Provides a read-only interface to Jira data for LLMs.
  • Allows natural language queries to retrieve live information from Jira.
  • Simplifies data access without requiring SQL knowledge.

Use cases of jira-mcp-server-by-cdata?

  1. Querying Jira for open tickets and their statuses.
  2. Analyzing project data and performance metrics.
  3. Integrating Jira data with AI applications for enhanced insights.

FAQ from jira-mcp-server-by-cdata?

  • Can I write data to Jira using this server?

No, this server is read-only and does not support write operations.

  • Is there a full version available?

Yes, a free beta version of the CData MCP Server for Jira with full read/write capabilities is available.

  • What programming language is this server built with?

The server is built using Java.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
0
Language
Java
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago