A Model-Context Protocol server for Amazon Redshift.
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":"redshift-comment-mcp","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.
# redshift-comment-mcp **English** · [日本語](README.ja.md) · [繁體中文](README.zh-TW.md) A read-only **Model Context Protocol** server for Amazon Redshift, plus a Claude Code plugin with 6 slash-command skills built on top. Designed around one assertion: **column names lie, comments don't** — so the server exposes comments aggressively and the skills compose those tools into the discovery workflows you actually do every day. ``` "What values does dbt_marts.fct_orders.status really hold?" → /redshift-profile dbt_marts.fct_orders status → cardinality, top-N, null rate, min/max, existing comment — one round. ``` ## Why this exists If you've ever opened an unfamiliar Redshift table and squinted at column names like `f3`, `legacy_id_v2`, or `status` (which `status`?), you already know the pain. dbt manifests are too narrow. Web GUIs are too slow. Hand-written SQL is too repetitive. This plugin's charter is **Guided Data Discovery**: - **Comments first.** Every list / search tool returns the column, table, or schema comment when asked — names are advisory, comments are authoritative. - **Read-only by construction.** `execute_sql` rejects DDL / DML at the parse layer; no skill in this repo can mutate Redshift. - **MCP-composed skills.** New workflows are built by stringing together existing tools, not by adding new database connections. - **No persistence.** No synthesis layer, no `.redshift-wiki/` markdown, no stale tracking. Persistence belongs in a separate plugin. See [`implementation_guide.md`](implementation_guide.md) §1.2 for the full charter. ## What you get ### MCP tools (13, defined in [`src/redshift_comment_mcp/`](src/redshift_comment_mcp/)) | Group | Tools | |---|---| | List | `list_schemas` · `list_tables` · `list_columns` | | Search (hit-count ranked) | `search_schemas` · `search_tables` · `search_columns` | | Comment retrieval | `get_schema_comment` · `get_table_comment` · `get_column_comment` · `get_all_column_comments` | | Query | `ex…
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.