JDBCX MCP Server

Created By
zhicwua year ago
Python MCP server for enabling data communication (databases, web services, scripts) via JDBCX server.
Overview

what is pydbcx-mcp?

pydbcx-mcp is a Python MCP server designed to facilitate communication with various data sources through a JDBCX server.

how to use pydbcx-mcp?

To use pydbcx-mcp, set up the server by following the installation instructions on the GitHub repository, and configure it to connect to your desired data sources.

key features of pydbcx-mcp?

  • Enables seamless communication with diverse data sources.
  • Built on Python for easy integration and customization.
  • Utilizes JDBCX for enhanced data connectivity.

use cases of pydbcx-mcp?

  1. Connecting Python applications to SQL databases via JDBC.
  2. Integrating data from multiple sources into a single application.
  3. Facilitating data analysis and reporting from various data sources.

FAQ from pydbcx-mcp?

  • What is JDBCX?

JDBCX is a protocol that allows for enhanced communication between applications and data sources.

  • Is pydbcx-mcp open source?

Yes! pydbcx-mcp is open source and available under the Apache-2.0 license.

  • How can I contribute to pydbcx-mcp?

You can contribute by submitting issues or pull requests on the GitHub repository.

Server Config

{
  "mcpServers": {
    "jdbcx": {
      "command": "uvx",
      "args": [
        "pydbcx-mcp"
      ],
      "env": {
        "DEFAULT_QUERY_TIMEOUT_SECONDS": "30",
        "JDBCX_SERVER_URL": "http://localhost:8080/",
        "JDBCX_SERVER_TOKEN": ""
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zhicwu
Star
0
Language
Python
License
Apache-2.0 license
Category
Tags

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago