Java based Model Context Procotol (MCP) Server for JDBC

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is OpenLinkSoftware_mcp-jdbc-server?

OpenLinkSoftware_mcp-jdbc-server is a lightweight Model Context Protocol (MCP) server for JDBC, designed to facilitate interactions with various database management systems (DBMS) using Java. It is particularly compatible with Virtuoso DBMS and other JDBC-compliant databases.

How to use OpenLinkSoftware_mcp-jdbc-server?

To use the MCP server, clone the repository from GitHub, configure the environment variables for your database connection, and run the server using Java. You can then connect to the server using compatible client applications.

Key features of OpenLinkSoftware_mcp-jdbc-server?

  • Fetch and list all schema names from the connected database.
  • Retrieve detailed information about tables, including column names and data types.
  • Execute SQL queries and stored procedures with results returned in various formats (JSONL, Markdown).
  • Filter and search for tables based on name substrings.
  • Interact with AI features through Virtuoso support.

Use cases of OpenLinkSoftware_mcp-jdbc-server?

  1. Connecting to and managing database schemas and tables.
  2. Executing complex SQL queries and retrieving structured results.
  3. Integrating with client applications for enhanced database interactions.
  4. Utilizing AI features for advanced data processing and querying.

FAQ from OpenLinkSoftware_mcp-jdbc-server?

  • What databases are supported?

The MCP server is compatible with any DBMS that has JDBC drivers, including Virtuoso.

  • Is there a specific Java version required?

Yes, the MCP server requires Java 21 or above.

  • How do I troubleshoot connection issues?

Use the MCP Inspector tool to diagnose and troubleshoot connections to the database.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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