AnalyticDB PostgreSQL MCP Server serves as a universal interface between AI Agents and AnalyticDB PostgreSQL databases. It enables seamless communication between AI Agents and AnalyticDB PostgreSQL, helping AI Agents retrieve database metadata and execute SQL operations.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"adbpg-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# AnalyticDB PostgreSQL MCP Server AnalyticDB PostgreSQL MCP Server serves as a universal interface between AI Agents and AnalyticDB PostgreSQL databases. It enables seamless communication between AI Agents and AnalyticDB PostgreSQL, helping AI Agents retrieve database metadata and execute SQL operations. ## Installation You can set up the server either from the source code for development or by installing it from PyPI for direct use. ### Option 1: From Source (for Development) This method is recommended if you want to modify or contribute to the server. ```shell # 1. Clone the repository git clone https://github.com/aliyun/alibabacloud-adbpg-mcp-server.git cd alibabacloud-adbpg-mcp-server # 2. Create and activate a virtual environment using uv uv venv .venv source .venv/bin/activate # On Linux/macOS # .\.venv\Scripts\activate # On Windows # 3. Install the project in editable mode uv pip install -e . ``` ### Option 2: From PyPI (for Production/Usage) This is the simplest way to install the server for direct use within your projects. ```shell pip install adbpg-mcp-server ``` ## Running the Server The server can be run in two transport modes: `stdio` (default) for integration with MCP clients, and `http` for direct API access or debugging. Make sure you have set up the required [Environment Variables](#environment-variables) before running the server. ### Stdio Mode (Default) This is the standard mode for communication with an MCP client. ```bash # Run using the default transport (stdio) uv run adbpg-mcp-server # Or explicitly specify the transport uv run adbpg-mcp-server --transport stdio ``` ### Streamable-HTTP Mode This mode exposes an HTTP server, which is useful for testing, debugging, or direct integration via REST APIs. ```bash # Run the server in HTTP mode on the default host and port (127.0.0.1:3000) uv run adbpg-mcp-server --transport http # Specify a custom host and port uv run adbpg-mcp-server --transport http --host 0.0.0.0 --port…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.