GitHub MCP Server by CData

Created By
CDataSoftwarea year ago
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 GitHub (beta): https://www.cdata.com/download/download.aspx?sku=FGZK-V&type=beta
Overview

What is GitHub MCP Server by CData?

GitHub MCP Server by CData is a read-only Model Context Protocol (MCP) server designed to allow large language models (LLMs) to query live data from GitHub using natural language, without the need for SQL.

How to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, build the server, install the CData JDBC Driver for GitHub, configure your connection, and create a configuration file for your AI client (e.g., Claude Desktop).

Key features of GitHub MCP Server?

  • Provides a read-only interface to GitHub data for LLMs.
  • Allows querying of live data using natural language.
  • Simplifies data access without requiring SQL knowledge.

Use cases of GitHub MCP Server?

  1. Querying GitHub repositories for specific information.
  2. Analyzing project data and statistics through natural language queries.
  3. Integrating GitHub data into AI applications for enhanced insights.

FAQ from GitHub MCP Server?

  • Can I write data to GitHub using this server?

No, this server is read-only. For write capabilities, consider the full CData MCP Server for GitHub.

  • Is there a trial version available?

Yes, you can access a free trial of the CData MCP Server for GitHub.

  • What programming languages are supported?

The server is built using Java and can be integrated with any language that can call Java applications.

Server Config

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\github.prp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
-
Language
-
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