siddharth-coder13/secure_schema_mcp — explained in plain English
Analysis updated 2026-05-18
Let an AI coding assistant see your database schema without ever touching real row data.
Restrict which tables are visible using a production allowlist.
Inspect one table's columns, keys, and relationships through a dedicated tool.
| siddharth-coder13/secure_schema_mcp | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs a reachable SQLite, PostgreSQL, or MySQL database and an MCP compatible IDE.
Secure Schema MCP is a read only server that lets AI coding tools like Cursor or Codex see the structure of a database without ever seeing the actual data inside it. Instead of returning rows or query results, it reports table and view names, column names and types, primary and foreign keys, and the relationships between tables, all formatted compactly to keep token usage low when an AI assistant reads it. The server connects to SQLite, PostgreSQL, or MySQL using a standard database connection URL, and it is designed to be run through uvx so you do not need to clone the repository or manage a Python environment yourself, your IDE just launches it automatically when needed. Configuration is done through environment variables, the most important being the database connection string and, for production use, a comma separated allowlist of which tables are visible at all. When that allowlist is set, requests for tables outside it are refused, and missing or disallowed tables return the same error message so nobody can guess which tables exist just from the error text. Three tools are exposed to the AI client: one giving a compact overview of all permitted tables and their relationships, one listing just the tables and views, and one describing a single table in detail including its columns and keys. The project's authors are direct about the residual risk: column names alone, such as one called ssn, can still reveal sensitive information, so they recommend a dedicated, low privilege database account and TLS for any remote connection, and warn against ever committing configuration files that contain real credentials.
A read only MCP server that gives AI coding tools a database's table and column structure without ever exposing the actual row data.
Mainly Python. The stack also includes Python, MCP, SQLAlchemy.
No license information is given in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.