The "Semantic Firewall" - JSqlParser validates that queries are in-fact queries, and therefore read-only, instead of relying on connection limits. Returning specific violations enables LLM self-correction for better success-per-prompt rates.
Dynamic Drivers - JDBC drivers loaded on-demand from Maven Central
Modular Architecture - Clean JPMS module structure utilizing SPI for extensible providers and zero compile-time dependencies.
Minimal Dependencies - No Spring, minimal CVE surface
jlink Ready - Build custom JVMs with only needed components
Client
The client should be able to run any mcp that uses the stdio transport. It's extremely helpful for debugging and building understanding of the mcp protocol.
JavaFX GUI - Modern, responsive interface
Tool Discovery - Automatically list server tools
Dynamic Forms - Auto-generated input forms from schemas
Pretty JSON - Formatted result display
Any MCP Server - Works with any MCP-compatible server that uses the stdio transport
Modules
These are the JPMS modules currently included. If you wanted to add your own tools, you would create a module that is an mcp provider.
Module
Purpose
jmcp-core
MCP protocol models and handlers
jmcp-transport-stdio
stdio transport implementation
jmcp-jdbc
JDBC tools, connection management, and driver loading
jmcp-server
Main server application
jmcp-client
JavaFX GUI client
Available Tools
Tool
Description
query
Execute a read-only SELECT query (up to 1000 rows)
explain-query
Get the execution plan for a SELECT query
get-row-count
Get the exact row count for a table
sample-data
Get sample rows from a table (first, random, or last; max 100)
analyze-column
Analyze a column: distinct count, nulls, min/max, top values
resource-proxy
A crucial workaround for clients without MCP resource support (like some IDE Copilots) — exposes robust database resource navigation directly via the tools API (implemented in jmcp-server, not jmcp-jdbc)
Available Resources
Resources provide navigable, HATEOAS-like access to database metadata. Start at db://context for a complete overview and follow the URIs to explore deeper.
Resource URI Pattern
Description
db://context
Complete database overview — the recommended starting point
Note: Clients that don't support the MCP resources protocol (e.g., some IDE Copilots) can access all resources via the resource-proxy tool.
Note:schema/{name} already embeds tables[]/views[]/procedures[] with navigation links, so a model that's already fetched a schema doesn't need the .../tables or .../views list resources — they add only REMARKS/TABLE_TYPE beyond what the schema resource already has.
"Human-in-the-Loop" Architecture & Testing
While this project accelerates development via AI assistance, its core value is the intentional, human-driven architecture.
JPMS & SPI: The server uses JPMS ServiceLoader (SPI) to discover transport and provider modules at
runtime. jmcp-server has no compile-time knowledge of specific tools or transports like jmcp-jdbc or
jmcp-transport-stdio — they are runtime dependencies only.
Test Suite: There are hundreds of test cases that the Semantic Firewall logic against basic DML/DDL rejection, complex bypass attempts, and dialect-specific edge cases to give users confidence.
Configuration
The server reads a single JSON config file and routes each top-level section to the
corresponding provider by JPMS module name. Create file at its default location for a quick start: ~/.jmcp/config.json:
JSON array of schema names to expose. When omitted, all schemas are visible. Recommended for large databases with many schemas.
Config file search order
System property: -Djmcp.config=/path/to/config.json
Default location: ~/.jmcp/config.json
HTTP Proxy for Driver Downloads
JDBC drivers are downloaded from Maven Central on first use. If your environment
requires an HTTP proxy, configure it using standard Java system properties or
environment variables — no changes to the config file are needed.
Java system properties (pass on the command line or in run.sh):
Downloads use HTTPS, so https.proxyHost/https.proxyPort are the standard
properties. http.proxyHost/http.proxyPort are also honored for
compatibility.
Environment variables (upper- or lower-case are both accepted; the value
must be http(s)://host[:port], port defaults to 80):
export HTTP_PROXY=http://proxy.example.com:8080
# or
export http_proxy=http://proxy.example.com:8080
Resolution order: https.proxyHost, then http.proxyHost, then HTTP_PROXY,
then HTTPS_PROXY. System properties always take precedence over environment
variables.
Proxies that require credentials (http://user:pass@host:port) are not
supported; such a value is ignored and a warning is logged.
Fail-fast initialization
If a provider's configure() throws — missing config, bad credentials, unreachable
database — the server prints the full stack trace and exits immediately. It will not
start in a degraded state. Providers must throw if they cannot be configured correctly.
Providers may also use their own configuration mechanisms (system properties,
environment variables, etc.) in addition to the server-supplied config map.
Requirements
Java 25+
Maven 3.9+
Network access to Maven Central: JDBC drivers are downloaded as needed
Security
The server enforces read-only access through:
SQL Validation - JSqlParser validates queries before execution, they must be read-only.
Read-Only Connections - HikariCP configured for read-only
Additionally, database users should have SELECT-only privileges.
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Jmcp कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Jmcp के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Jmcp कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Jmcp stdio पर लोकल चलता है।
Jmcp की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-28 को हुई। read only database mcp server with extensible framework