MCP server for YugabyteDB/PostgreSQL — read and write tools, optional OAuth
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":"yugabytedb-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.
# YugabyteDB MCP Server An [MCP](https://modelcontextprotocol.io/) server for YugabyteDB and PostgreSQL — lets LLMs (Claude Desktop, Cursor, Windsurf, etc.) summarize schemas, run read-only queries, and execute write statements behind a configurable guardrail layer. ## Features - **`summarize_database`** — list tables with columns and row counts for a schema (read-only) - **`run_read_only_query`** — execute a SELECT under `BEGIN READ ONLY`; results returned as JSON (read-only) - **`run_write_query`** — INSERT/UPDATE/DELETE/MERGE/TRUNCATE/DDL gated by a guardrail blocklist (destructive) Defense in depth: the write tool is annotated `destructiveHint: true`, so Claude Desktop surfaces a confirmation prompt before every call even when the guardrails would let the statement through. Optional OAuth (AWS Cognito) and Origin-header validation for self-hosted remote deployments. ## Prerequisites - Python 3.10+ - [uv](https://docs.astral.sh/uv/) (recommended) or pip - A reachable YugabyteDB or PostgreSQL database - An MCP client (Claude Desktop, Cursor, Windsurf, etc.) ## Installation Three install options, in roughly the order of how end users will reach for them: ```bash # uvx — no install at all; fetches and runs on demand. Handy for one-off use # and also the form the MCPB Desktop extension uses internally. uvx yugabytedb-mcp-server --help # pipx — installs to an isolated venv, puts the script on $PATH. pipx install yugabytedb-mcp-server # uv tool — same idea, uv-managed. uv tool install yugabytedb-mcp-server # pip — system-level or current-venv install. pip install yugabytedb-mcp-server ``` After any of the persistent installs (pipx / uv tool / pip), verify with: ```bash yugabytedb-mcp --help # or, equivalently: yugabytedb-mcp-server --help ``` Both console scripts are registered and point at the same entry point — `yugabytedb-mcp` is the short form, `yugabytedb-mcp-server` matches the package name and is what `uvx` resolves to by default. > **Pre-relea…
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.