Huawei Cloud RDS Supabase MCP Server
Data-plane MCP server for Huawei Cloud RDS Supabase — a cloud-managed, self-hosted Supabase deployment whose database is an RDS PostgreSQL instance reached through the Kong gateway (PostgREST RPC). It gives AI assistants safe in-database operations: SQL execution via a hardened RPC function, schema inspection, auth-user management, storage configuration and security checks, behind three-tier risk guardrails.
Version
Current version: 0.4.3; Python 3.10+; MCP Python SDK 2.x; transports: stdio and Streamable HTTP; license: Apache-2.0 (see repository NOTICE for the MIT derivation chain of the upstream TypeScript project).
Overview
This server runs on the shared
huaweicloud_mcp_core runtime: three-layer architecture (tools → service →
client), three-tier risk guardrails (READ / WRITE / DANGEROUS lanes, read-only
mode, protection lists, structured audit), and a hardened in-database
execute_sql RPC function. All tool names, parameters, defaults, return
shapes and error messages are kept identical to the upstream TypeScript
server; the adaptation adds the platform guardrail layer on top.
Installation
Published on PyPI — one command runs it (no checkout, no pip):
uvx mcp-server-huaweicloud-rds-supabase
Or install then run:
pip install mcp-server-huaweicloud-rds-supabase
mcp-server-huaweicloud-rds-supabase
From the source workspace:
cd /absolute/path/to/rds-supabase-fullstack/server/mcp_server_rds_supabase
uv sync --frozen
uv run mcp-server-huaweicloud-rds-supabase
Quick start
# Read-only mode against a running instance.
# SUPABASE_URL is the Kong gateway address: http(s)://<rds_supabase_eip>:<rds_supabase_port>
# <rds_supabase_eip> the elastic public IP bound to the RDS Supabase
# application (the "public_ip" in the application detail)
# <rds_supabase_port> the Kong gateway entry port, fixed at 8443
# http(s) https with the SSL switch on, http otherwise
# Filled example below: SSL disabled, EIP 123.60.101.251
HUAWEICLOUD_MCP_READ_ONLY=true \
SUPABASE_URL=http://123.60.101.251:8443 \
SUPABASE_ANON_KEY=<anon-key> \
SUPABASE_SERVICE_ROLE_KEY=<service-role-key> \
uvx mcp-server-huaweicloud-rds-supabase
Standard stdio client configuration (template):
{
"mcpServers": {
"rds-supabase": {
"command": "uvx",
"args": [
"mcp-server-huaweicloud-rds-supabase"
],
"env": {
"SUPABASE_URL": "http(s)://<rds_supabase_eip>:<rds_supabase_port>",
"SUPABASE_ANON_KEY": "<anon-key>",
"SUPABASE_SERVICE_ROLE_KEY": "<service-role-key>"
}
}
}
}
Template parameters:
<rds_supabase_eip>— the elastic public IP bound to the RDS Supabase application (thepublic_ipshown in the application detail; without a bound EIP the instance is reachable only from inside the VPC)<rds_supabase_port>— the Kong gateway entry port, fixed at 8443http(s)— protocol follows the application SSL switch:httpswhen enabled,httpwhen not<anon-key>(SUPABASE_ANON_KEY) — the anonymous API key: an anon-role JWT starting witheyJ<service-role-key>(SUPABASE_SERVICE_ROLE_KEY) — the service_role API key (JWT starting witheyJ); required forexecute_sqland auth-user management; it bypasses RLS — trusted environments only
Filled example (SSL disabled, EIP 123.60.101.251, port 8443):
{
"mcpServers": {
"rds-supabase": {
"command": "uvx",
"args": [
"mcp-server-huaweicloud-rds-supabase"
],
"env": {
"SUPABASE_URL": "http://123.60.101.251:8443",
"SUPABASE_ANON_KEY": "<anon-key>",
"SUPABASE_SERVICE_ROLE_KEY": "<service-role-key>"
}
}
}
}
Category
Database / self-hosted Supabase on managed PostgreSQL / operations automation.
Features
- 38 tools across six families — database, project, auth users, storage, platform and inspection — with stable names, parameters, defaults, return shapes and error messages.
- SQL execution over the Kong gateway via the hardened
execute_sqlRPC (service-role key) with an in-databaseread_onlystatement whitelist; direct database connections are not supported. - Shared-core guardrails: risk lanes per tool, read-only mode, guardrail rules (block / confirm / warn), protected lists, JSONL audit, output masking.
- Tools-config whitelist (
{"enabledTools": [...]}) with upstream fallback semantics. - Startup probe of the
execute_sqlfunction (deploysql/mcp-execute-sql.sqlonce via the management console). - Dual transport (stdio and Streamable HTTP) with the standard runner.
Available Tools
| Tool | Purpose | Risk |
|---|---|---|
list_tables |
List accessible tables grouped by schema | READ |
list_extensions |
List installed PostgreSQL extensions | READ |
execute_sql |
Run arbitrary SQL via the hardened RPC (service-role key); deploys init.sql migration batches and their companion cleanup scripts (deletion scenarios, on user request) | WRITE |
get_database_connections |
Active client backends from pg_stat_activity | READ |
get_database_stats |
pg_stat_database + pg_stat_bgwriter snapshot | READ |
get_project_url |
Return the configured Supabase project URL | READ |
generate_typescript_types |
Generate TS types via the Supabase CLI | WRITE |
rebuild_hooks |
Restart the pg_net worker | WRITE |
verify_jwt_secret |
Check whether the JWT secret is configured | READ |
list_auth_users |
List auth users via the auth admin API | READ |
get_auth_user |
Fetch one auth user by ID (auth admin API) | READ |
delete_auth_user |
Delete an auth user by ID (auth admin API) | WRITE |
create_auth_user |
Create an auth user (auth admin API, hashing by GoTrue) | WRITE |
update_auth_user |
Update auth user fields (auth admin API) | WRITE |
list_storage_buckets |
List storage buckets (direct-connection channel, unavailable in this deployment) | READ |
list_storage_objects |
List objects in a bucket with prefix filter | READ |
list_realtime_publications |
List publications (direct-connection channel, unavailable in this deployment) | READ |
list_cron_jobs |
List pg_cron jobs (empty when not installed) | READ |
list_vector_indexes |
List ivfflat / hnsw indexes | READ |
get_logs |
Service logs (analytics → CSV → none cascade) | READ |
get_advisors |
Security / performance advisory checks | READ |
get_storage_config |
Storage bucket configuration | READ |
update_storage_config |
Update bucket limits / MIME types / visibility | WRITE |
list_table_columns |
Column metadata for a table | READ |
list_indexes |
Indexes with definitions and sizes | READ |
list_constraints |
PK / FK / UNIQUE / CHECK / EXCLUDE constraints | READ |
list_foreign_keys |
Foreign-key relationships | READ |
list_rls_policies |
Row Level Security policies | READ |
list_triggers |
Table triggers | READ |
list_database_functions |
User-defined functions | READ |
get_function_definition |
Full source of a database function | READ |
get_trigger_definition |
Full definition of a trigger | READ |
get_rls_status |
RLS enablement status per table | READ |
list_available_extensions |
Extensions available for installation | READ |
get_cron_job_history |
pg_cron job execution history | READ |
get_index_stats |
Usage statistics for one index | READ |
get_vector_index_stats |
Usage statistics for vector indexes | READ |
explain_query |
EXPLAIN a query with optional ANALYZE | READ |
Seven tools mutate state (WRITE): execute_sql,
generate_typescript_types, rebuild_hooks, delete_auth_user,
create_auth_user, update_auth_user and update_storage_config. Upstream
tools carry no confirm parameter, so no tool is classified DANGEROUS — the
default behaviour stays identical to the TypeScript server. Operators who
want explicit confirmation can add a confirm guardrail rule (see
Configuration) without changing tool signatures.
execute_sql channel and the hardened function
execute_sql calls the public.execute_sql(query, read_only) RPC with the
service-role key — the only supported SQL channel. The repo ships the hardened
function definition at sql/mcp-execute-sql.sql (service_role-only access,
in-database read_only statement whitelist, first-keyword dispatch, grants
restricted to service_role). Deploy it once through the cloud management
console (for example the postgres-meta /pg/query channel); the server probes
for it at startup and logs a warning until it is deployed.
Usage Guide
Prerequisites
- Python 3.10+ and uv
- A running RDS Supabase (or self-hosted Supabase) instance
- An anon key plus a service-role key (SQL channel + auth admin API); direct database connections are not supported
Installation
# uvx (no checkout)
uvx mcp-server-huaweicloud-rds-supabase
# pip from a checkout
pip install ./server/mcp_server_rds_supabase
Configuration
| Variable | Required | Description |
|---|---|---|
SUPABASE_URL |
Yes | Kong gateway address: http(s)://<rds_supabase_eip>:<rds_supabase_port> — parameters explained under Quick start |
SUPABASE_ANON_KEY |
Yes | Anonymous key |
SUPABASE_SERVICE_ROLE_KEY |
No | Service-role key; enables the RPC SQL channel |
SUPABASE_AUTH_JWT_SECRET |
No | JWT secret (checked by verify_jwt_secret) |
RDS_SUPABASE_WORKSPACE_PATH |
No | Workspace root for file outputs (default: cwd) |
RDS_SUPABASE_TOOLS_CONFIG |
No | Path to {"enabledTools": [...]} JSON whitelist |
HUAWEICLOUD_MCP_READ_ONLY |
No | true blocks every WRITE tool |
HUAWEICLOUD_MCP_GUARDRAILS_CONFIG |
No | YAML guardrail rules (block / confirm / warn) |
HUAWEICLOUD_MCP_PROTECTED_IDS |
No | Comma-separated protected resource IDs |
HUAWEICLOUD_MCP_PROTECTED_NAMES |
No | Comma-separated protected names |
HUAWEICLOUD_MCP_PROTECTED_TAGS |
No | Comma-separated protected tags |
HUAWEICLOUD_MCP_AUDIT_FILE |
No | JSONL audit file (audit always emits to stderr) |
MCP_SERVER_HOST / MCP_SERVER_PORT |
No | Streamable HTTP listen address (0.0.0.0:8000) |
Notes:
- Without
SUPABASE_SERVICE_ROLE_KEY, SQL tools return a configuration error. Storage/publication listing tools report that direct connections are unsupported (RPC rework pending). Auth user tools use the auth admin API (service-role key only). - The guardrail middleware masks secret-like keys and values in tool output (a shared-core security property that cannot be disabled).
- A
confirmrule example: requests confirmation before everyexecute_sqlexecution while leaving all tool signatures unchanged.
rules:
- id: confirm-execute-sql
action: confirm
message: "Review the SQL statement before executing it."
match:
tools: ["execute_sql"]
Run with UVX
MCP_SERVER_HOST=0.0.0.0 MCP_SERVER_PORT=8000 \
uvx mcp-server-huaweicloud-rds-supabase -t streamable-http
The Streamable HTTP endpoint is /mcp. Protect it at the network layer: the
upstream TypeScript HTTP auth middleware (JWT bearer, role privileges, CORS,
rate limiting) is not part of this port — stdio is the primary transport.
Examples
Inspect schema, then verify RLS posture:
list_tables→ discoverpublic.studentsget_rls_status→ check whether RLS is enabledget_advisorswithtype="security"→ review advisory issuesexecute_sqlwithread_only=truefor further SELECT investigation
Client compatibility
| Client | Transport | Notes |
|---|---|---|
| Any MCP client (Claude Code, opencode, AgentArts, ...) | stdio | Primary mode |
| HTTP clients | Streamable HTTP | Endpoint /mcp; add network auth |
Permissions
- Read-only operations: anon key + service-role key for the RPC channel.
- Write operations (7 WRITE tools): service-role key, the only privileged
channel; consider
HUAWEICLOUD_MCP_READ_ONLY=truefor inspection-only agents. - Only the service-role key is required (RPC + auth admin API channels).
Development, testing, and release
uv sync --frozen --all-packages --all-groups
uv run --package mcp-server-huaweicloud-rds-supabase ruff check server/mcp_server_rds_supabase/src server/mcp_server_rds_supabase/tests
(cd server/mcp_server_rds_supabase && uv run --package mcp-server-huaweicloud-rds-supabase mypy src)
uv run --package mcp-server-huaweicloud-rds-supabase pytest server/mcp_server_rds_supabase/tests
uv build --package huaweicloud-mcp-core && uv build --package mcp-server-huaweicloud-rds-supabase
241 tests, coverage gate 90% (currently 94%). E2E validation evidence lives
in docs/validation/ at the repository root.
Contributing and support
See the repository root CONTRIBUTING.md. Report security issues privately via SECURITY.md; never paste keys into issues.
License
Apache License 2.0. The Python implementation derives from the MIT-licensed
upstream rds-supabase-mcp (HenkDz and contributors); see NOTICE.
Metadata
Release files for mcp-server-huaweicloud-rds-supabase 0.4.5
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 | Actions |
|---|---|---|---|---|
| mcp_server_huaweicloud_rds_supabase-0.4.5.tar.gz | 43.2 kB | Without provenance | Details for mcp_server_huaweicloud_rds_supabase-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_server_huaweicloud_rds_supabase-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for mcp_server_huaweicloud_rds_supabase-0.4.5-py3-none-any.whl |
Total release size: 90.4 kB
Release files / mcp_server_huaweicloud_rds_supabase-0.4.5.tar.gz
| Download URL | mcp_server_huaweicloud_rds_supabase-0.4.5.tar.gz |
|---|---|
| Size | 43.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcebe269ea017ead722b0e121bd47c471253a5cc634cbf868020c3f3814e6dfd
|
|
BLAKE2b-256 checksum How to use checksums |
a5d17b40ecd372690f5dd3700d97c56c6bb3fe7e2be60031a35c946db8e87b3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_server_huaweicloud_rds_supabase-0.4.5-py3-none-any.whl
| Download URL | mcp_server_huaweicloud_rds_supabase-0.4.5-py3-none-any.whl |
|---|---|
| Size | 47.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
527159fb99a21e5c60d0ac9900cd207bfc7a76e5591bd36ab490b2fc27531597
|
|
BLAKE2b-256 checksum How to use checksums |
c11e962b13dccddccc29c17aa90bf5253a60c15402713e27a2f976f0ffc1b2f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-server-huaweicloud-rds-supabase 0.4.5
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.