JDBCX MCP Server
pydbcx-mcp is a Python implementation of MCP server for enabling communication with diverse data sources via JDBCX server.
Installation
Start JDBCX server
Starts the JDBCX server container. Check out here for more information.
# Start the server
docker run --rm --name bridge -d -p8080:8080 jdbcx/jdbcx server
# Test if the server if ready
curl -v 'http://localhost:8080/config'
# Check server logs
docker logs --tail=100 -f bridge
# Shutdown the server
docker stop bridge
Configure MCP server
To install JDBCX MCP server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @jdbcx/pydbcx-mcp --client claude
Alternatively, add the MCP server into your JSON config file.
Development/Unpublished Server Configuration
{
"mcpServers": {
"jdbcx": {
"command": "uv",
"args": [
"--directory",
"</path/to/your/pydbcx-mcp/dir>",
"run",
"pydbcx-mcp"
],
"env": {
"DEFAULT_QUERY_TIMEOUT_SECONDS": "30",
"JDBCX_SERVER_URL": "http://localhost:8080/",
"JDBCX_SERVER_TOKEN": "",
"MAX_ROWS_LIMIT": "5000"
}
}
}
}
Published Server Configuration
{
"mcpServers": {
"jdbcx": {
"command": "uvx",
"args": ["pydbcx-mcp"],
"env": {
"DEFAULT_DATA_FORMAT": "md"
}
}
}
}
Published SSE Server Configuration
{
"mcpServers": {
"jdbcx": {
"url": "http://localhost:8080/sse"
}
}
}
Note: remember to start the SSE server first by JDBCX_SERVER_URL=http://localhost:8080/ DEFAULT_QUERY_TIMEOUT_SECONDS=30 uvx pydbcx-mcp --transport sse.
Configuration
Configure the server using environment variables:
| Variable | Description | Default |
|---|---|---|
JDBCX_LOG_LEVEL |
Log level | DEBUG |
JDBCX_SERVER_URL |
JDBCX server URL | http://localhost:8080 |
JDBCX_SERVER_TOKEN |
JDBCX server access token | None |
DEFAULT_ACCEPT_ENCODING |
Default accept-encoding | identity |
DEFAULT_QUERY_TIMEOUT_SECONDS |
Default query timeout (seconds) | 10 |
DEFAULT_DATA_FORMAT |
Default data format (md, jsonl, csv) | csv |
DEFAULT_ROWS_LIMIT |
Default number of rows can be returned | 100 |
MAX_ROWS_LIMIT |
Maximum number of rows can be returned | 1000 |
MCP_TRANSPORT |
MCP server transport (stdio, see) | stdio |
MCP_SERVER_HOST |
MCP server listening address | 0.0.0.0 |
MCP_SERVER_PORT |
MCP server listening port | 8080 |
MCP_SERVER_NAME |
MCP server name | JDBCX MCP Server |
Note: It is highly recommended to enable access token in JDBCX server and configure JDBCX_SERVER_TOKEN accordingly for security reason.
Metadata
Release files for pydbcx-mcp 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pydbcx_mcp-0.1.3.tar.gz | 45.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydbcx_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.8 kB
Release files / pydbcx_mcp-0.1.3.tar.gz
| Download URL | pydbcx_mcp-0.1.3.tar.gz |
|---|---|
| Size | 45.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f56fd220bd91a1a0e8745faca1156a79dd954ad163252c4e55cdf1673dfce54
|
|
BLAKE2b-256 checksum How to use checksums |
416f6cf0fdb5f446d62bb05a79af5dad310c8ba56d1fd1feabfa75c7be399e1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.3
|
Release files / pydbcx_mcp-0.1.3-py3-none-any.whl
| Download URL | pydbcx_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7d715fe63be7b67899deb72cc2fe30f4527f7f98db7f685ab6c8db682b8d630
|
|
BLAKE2b-256 checksum How to use checksums |
0d42036d3b6a20bf9a0b910bd82107e6f9062344dbd95a8c4c47f5c7bdf10d50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.3
|
Security for pydbcx-mcp 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.