Production MCP server for Postgres, Oracle, Snowflake, BigQuery, Redshift, DuckDB, MotherDuck.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Production MCP (Model Context Protocol) server for your data warehouse. Read-only enforcement, five-tier role-based access, optional warehouse-role impersonation (for native RLS / CLS), JSONL audit log, optional output PII masking, optional semantic-metadata layer (glossary + table docs) with per-session toggle. Self-host the Docker image, install via npx, or wait for the upcoming managed cloud variant.
Status: v0.4.x β production-ready for the v1 warehouse list. See CHANGELOG for what shipped in each release.
Warehouse MCP in action using Cursor
| Warehouse | Adapter docs |
|---|---|
| Postgres 12+ | docs/adapters/postgres.md |
| Oracle 12c+ (Thin mode, no Instant Client) | docs/adapters/oracle.md |
| Amazon Redshift (cluster + Serverless) | docs/adapters/redshift.md |
| Snowflake (key-pair auth) | docs/adapters/snowflake.md |
| Google BigQuery | docs/adapters/bigquery.md |
DuckDB (local file or :memory:) | docs/adapters/duckdb.md |
MotherDuck (cloud-hosted DuckDB, md: paths) | docs/adapters/duckdb.md |
Databricks SQL is a fast-follow.
| Tool | Purpose |
|---|---|
query | Execute a SELECT (validator-enforced read-only, dialect-aware) |
list_schemas, list_tables, describe_table | Browse the catalog |
find_columns | Search column names across the warehouse with a LIKE pattern |
get_foreign_keys | Discover declared FK relationships for safe joins |
get_view_definition | Read the SQL body of a view (where business logic lives) |
sample_table, count_rows | Peek at data, check size before scanning |
column_stats, top_values | Profile a single column |
time_series | Bucket by hour/day/week/month/quarter/year β dialect-correct everywhere |
search_value | Find a literal across a table's text columns |
glossary_lookup | Read business-glossary terms from the semantic layer (in-memory, no warehouse I/O) |
schema_lookup | Read schema-level docs β purpose, owner, refresh, table list |
table_lookup | Read full semantic doc for one table β description + column metadata |
| Role | Tools allowed |
|---|---|
semantic_only | Only the three semantic-lookup tools β zero warehouse access; pair with semantic=on for a docs-viewer persona |
metadata_only | Catalog discovery + semantic lookups β never reads row data |
reader_restricted | Aggregates / samples / time series β no arbitrary SELECT |
reader | Adds query and search_value (the general analyst tier) |
admin | Everything; future write tools when ENABLE_WRITE_TOOLS ships |
Per-key role assigned via MCP_API_KEYS=key:role[:set_role=warehouse_role][:semantic=on|off]. The optional set_role= directive issues SET ROLE on Postgres/Redshift so the warehouse's own RLS / CLS / masking policies enforce per-key access β no policy duplication in MCP. The optional semantic=on|off directive overrides SEMANTIC_DEFAULT for that one key, controlling whether the session sees the warehouse://semantic/* resources (see docs/semantic-metadata.md).
For deployments with multiple existing DB roles (finance, hr, payroll, etc.) and many human users, see docs/multi-role-deployment.md β walks through mapping ~10 DB roles to MCP keys, the recommended <area> / <area>_restricted pattern, and when to graduate from static keys to OIDC.
{ "mcpServers": { "warehouse-admin-semanticon": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer admin-key-change-me" ] }, "warehouse-admin-semanticoff": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer admin-key-nosemantic" ] }, "warehouse-reader-semanticon": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer reader-key-change-me" ] }, "warehouse-reader-semanticoff": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer reader-key-nosemantic" ] }, "warehouse-reader-restricted-semanticon": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer restricted-key-change-me" ] }, "warehouse-reader-restricted-semanticoff": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer restricted-key-nosemantic" ] }, "warehouse-metadata-only-semanticon": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer metadata-only-key-change-me" ] }, "warehouse-metadata-only-semanticoff": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer metadata-only-key-nosemantic" ] }, "warehouse-docs-viewer-only": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "http://localhost:3001/mcp", "--header", "Authorization: Bearer docs_viewer_key_change_me" ] } } }
The same image bundles every adapter; pick one with WAREHOUSE_TYPE plus the matching credentials. For credentials, prefer --env-file (or your secrets manager) over inline -e flags so passwords don't end up in shell history.
Then point an AI client at it. Drop-in configs:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/warehouse-mcp)<a href="https://allmcps.com/mcp/warehouse-mcp"><img src="https://allmcps.com/api/badge/warehouse-mcp?style=directory" alt="Warehouse MCP on AllMCPs" /></a>