English Français العربية

SQLBot MCP Proxy

Official registry Data and databases

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

Source code Documentation

What can you do with SQLBot MCP Proxy?

  • 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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

OCI package ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0
Claude Code 
claude mcp add sqlbot-mcp-proxy -e 'SQLBOT_MCP_PROXY_BASE_URL=<SQLBOT_MCP_PROXY_BASE_URL>' -e 'SQLBOT_MCP_PROXY_ACCESS_KEY=<your sqlbot_mcp_proxy_access_key>' -e 'SQLBOT_MCP_PROXY_SECRET_KEY=<your sqlbot_mcp_proxy_secret_key>' -e 'SQLBOT_MCP_PROXY_DOCKER_CONTAINER=<SQLBOT_MCP_PROXY_DOCKER_CONTAINER>' -- docker run -i --rm ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "sqlbot-mcp-proxy": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0"
            ],
            "env": {
                "SQLBOT_MCP_PROXY_BASE_URL": "<SQLBOT_MCP_PROXY_BASE_URL>",
                "SQLBOT_MCP_PROXY_ACCESS_KEY": "<your sqlbot_mcp_proxy_access_key>",
                "SQLBOT_MCP_PROXY_SECRET_KEY": "<your sqlbot_mcp_proxy_secret_key>",
                "SQLBOT_MCP_PROXY_DOCKER_CONTAINER": "<SQLBOT_MCP_PROXY_DOCKER_CONTAINER>"
            }
        }
    }
}

Environment variables

  • SQLBOT_MCP_PROXY_BASE_URL Base URL of the SQLBot service, for example http://127.0.0.1:8000.
  • SQLBOT_MCP_PROXY_ACCESS_KEY secret SQLBot API access key. If omitted, the proxy can try FEISHU_ASK_ACCESS_KEY or read from the configured Docker container.
  • SQLBOT_MCP_PROXY_SECRET_KEY secret SQLBot API secret key. If omitted, the proxy can try FEISHU_ASK_SECRET_KEY or read from the configured Docker container.
  • SQLBOT_MCP_PROXY_DOCKER_CONTAINER Optional Docker container name used when reading FEISHU_ASK_ACCESS_KEY and FEISHU_ASK_SECRET_KEY from a running SQLBot container.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. SQLBot MCP Proxy
  2. Requirements
  3. Recommended Codex Config
  4. Prompt Template
  5. Quick Docker Test
  6. Tools
  7. Environment Variables
  8. Advanced HTTP Mode
  9. Publish

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

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

[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 = true
startup_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

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:

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:

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:

curl http://127.0.0.1:8787/health

Publish

  1. Confirm package metadata in package.json.
  2. Publish an OCI image:
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:
mcp-publisher login github
mcp-publisher publish

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

Frequently asked questions

What is SQLBot MCP Proxy?

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

How do I install SQLBot MCP Proxy?

It runs on your machine. In Claude Code: claude mcp add sqlbot-mcp-proxy -e 'SQLBOT_MCP_PROXY_BASE_URL=<SQLBOT_MCP_PROXY_BASE_URL>' -e 'SQLBOT_MCP_PROXY_ACCESS_KEY=<your sqlbot_mcp_proxy_access_key>' -e 'SQLBOT_MCP_PROXY_SECRET_KEY=<your sqlbot_mcp_proxy_secret_key>' -e 'SQLBOT_MCP_PROXY_DOCKER_CONTAINER=<SQLBOT_MCP_PROXY_DOCKER_CONTAINER>' -- docker run -i --rm ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does SQLBot MCP Proxy need an API key?

Yes. It expects SQLBOT_MCP_PROXY_ACCESS_KEY, SQLBOT_MCP_PROXY_SECRET_KEY, which you set in its configuration.

Is SQLBot MCP Proxy open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains SQLBot MCP Proxy?

It is published by wenRou21. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.