SQLBot MCP Proxy

io.github.wenRou21Published by GitHub account wenRou21v0.1.0Updated Oct 24, 2026

MCP server proxy for SQLBot Text-to-SQL queries and report generation.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Proxy MCP server that lets an assistant explore SQLBot datasources and tables, ask natural-language data questions, and generate analysis reports.

What you can do
  • List datasources visible to the configured SQLBot API key
  • List checked metadata tables for a datasource and describe their fields
  • Ask SQLBot a natural-language data question (Text-to-SQL)
  • Generate an analysis report and chart, with a local SVG fallback written to an output directory
When to use it
Useful when you already run a SQLBot service and want an assistant to query its data in plain language, inspect table metadata first, and produce quick analysis reports or charts without writing SQL by hand.
Requirements
Docker, since the server runs as an OCI image (ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0) via docker run. A reachable SQLBot service URL in SQLBOT_MCP_PROXY_BASE_URL, plus SQLBot API credentials in SQLBOT_MCP_PROXY_ACCESS_KEY and SQLBOT_MCP_PROXY_SECRET_KEY. Optional fallback keys FEISHU_ASK_ACCESS_KEY and FEISHU_ASK_SECRET_KEY, or reading keys from a running container named by SQLBOT_MCP_PROXY_DOCKER_CONTAINER.
Before you install
Requires SQLBot API access and secret keys, which are passed as environment variables into the container; the README's example config also embeds a public IP address that should be replaced with your own service. Queries and report requests are sent to the configured SQLBot service, so data leaves your machine. Generated fallback SVG reports are written to a local output directory. The optional container key lookup reads credentials from a running Docker container.

Installation

In SourceWeft

  1. Open SQLBot MCP Proxy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SQLBot MCP Proxy

MCP server proxy for SQLBot. It exposes SQLBot datasource discovery, table metadata, natural-language Text-to-SQL questions, and local fallback report generation as MCP tools.

Requirements

  • Docker
  • A running SQLBot service
  • SQLBot API keys

Recommended Codex Config

Users do not need to download this repository manually. Add this single MCP server to Codex config and replace the SQLBot URL and keys:

toml
[mcp_servers.sqlbot]command = "docker"args = [  "run",  "--rm",  "-i",  "-e",  "SQLBOT_MCP_PROXY_BASE_URL",  "-e",  "SQLBOT_MCP_PROXY_ACCESS_KEY",  "-e",  "SQLBOT_MCP_PROXY_SECRET_KEY",  "ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0"]enabled = truestartup_timeout_sec = 120
[mcp_servers.sqlbot.env]SQLBOT_MCP_PROXY_BASE_URL = "http://183.196.108.32:18088"SQLBOT_MCP_PROXY_ACCESS_KEY = "<YOUR_SQLBOT_ACCESS_KEY>"SQLBOT_MCP_PROXY_SECRET_KEY = "<YOUR_SQLBOT_SECRET_KEY>"

Then restart Codex completely.

If SQLBot is reachable through another public or LAN address, replace SQLBOT_MCP_PROXY_BASE_URL with that address, for example https://sqlbot.example.com or http://192.168.1.10:18088.

Prompt Template

text
Please configure SQLBot MCP for Codex.
MCP image:ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0
My SQLBot URL:http://183.196.108.32:18088
My SQLBot access key:<YOUR_SQLBOT_ACCESS_KEY>
My SQLBot secret key:<YOUR_SQLBOT_SECRET_KEY>
Add this MCP to Codex config:- MCP name: sqlbot- command: docker- args: ["run", "--rm", "-i", "-e", "SQLBOT_MCP_PROXY_BASE_URL", "-e", "SQLBOT_MCP_PROXY_ACCESS_KEY", "-e", "SQLBOT_MCP_PROXY_SECRET_KEY", "ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0"]- startup_timeout_sec: 120- SQLBOT_MCP_PROXY_BASE_URL: use the SQLBot URL above- SQLBOT_MCP_PROXY_ACCESS_KEY: use the access key above- SQLBOT_MCP_PROXY_SECRET_KEY: use the secret key above
After configuration, remind me to fully restart Codex.
After restart:- Check available datasources with sqlbot_list_datasources.- Use sqlbot_list_tables and sqlbot_describe_table before asking data questions.- Use sqlbot_ask_data for Text-to-SQL questions.- Use sqlbot_generate_report when I ask for an analysis report or chart.

Quick Docker Test

You can test the image outside Codex:

bash
docker run --rm -i \  -e SQLBOT_MCP_PROXY_BASE_URL=http://183.196.108.32:18088 \  -e SQLBOT_MCP_PROXY_ACCESS_KEY=your-access-key \  -e SQLBOT_MCP_PROXY_SECRET_KEY=your-secret-key \  ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0

Tools

  • sqlbot_list_datasources: list SQLBot datasources visible to the configured API key
  • sqlbot_list_tables: list checked SQLBot metadata tables for a datasource
  • sqlbot_describe_table: describe checked fields for a SQLBot metadata table
  • sqlbot_ask_data: ask SQLBot a natural-language data question
  • sqlbot_generate_report: generate an analysis report and chart, with a local SVG fallback

Environment Variables

NameDefaultDescription
SQLBOT_MCP_PROXY_BASE_URLhttp://183.196.108.32:18088SQLBot service base URL
SQLBOT_MCP_PROXY_ACCESS_KEYemptySQLBot API access key
SQLBOT_MCP_PROXY_SECRET_KEYemptySQLBot API secret key
FEISHU_ASK_ACCESS_KEYemptyFallback access key name
FEISHU_ASK_SECRET_KEYemptyFallback secret key name
SQLBOT_MCP_PROXY_DOCKER_CONTAINERsqlbotContainer used for fallback key lookup
SQLBOT_MCP_PROXY_HTTP_HOST127.0.0.1HTTP mode host
SQLBOT_MCP_PROXY_HTTP_PORT8787HTTP mode port
SQLBOT_MCP_PROXY_HTTP_PATH/mcpHTTP mode JSON-RPC path
SQLBOT_MCP_PROXY_HTTP_TIMEOUT_MS120000SQLBot HTTP request timeout
SQLBOT_MCP_PROXY_REPORT_OUTPUT_DIRoutputsDirectory for generated fallback SVG reports

Advanced HTTP Mode

Most MCP clients should use stdio. For clients that can send JSON-RPC over HTTP, start:

bash
docker run --rm -p 8787:8787 \  -e SQLBOT_MCP_PROXY_BASE_URL=http://183.196.108.32:18088 \  -e SQLBOT_MCP_PROXY_ACCESS_KEY=your-access-key \  -e SQLBOT_MCP_PROXY_SECRET_KEY=your-secret-key \  -e SQLBOT_MCP_PROXY_HTTP_HOST=0.0.0.0 \  ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0 --http

Health check:

bash
curl http://127.0.0.1:8787/health

Publish

  1. Confirm package metadata in package.json.
  2. Publish an OCI image:
bash
docker build -t ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0 .docker push ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0
  1. Publish MCP Registry metadata:
bash
mcp-publisher login githubmcp-publisher publish

The mcpName in package.json must exactly match name in server.json.

Source: README.md at commit 1e66dcf

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts