Secure Schema MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | SQLAlchemy connection URL. Treated as a secret by the registry manifest. | |
| ALLOWED_TABLES | No | Comma-separated, case-sensitive table and view allowlist. Production mode refuses to start without it. | |
| DATABASE_SCHEMA | No | Default schema or catalog namespace. Recommended for PostgreSQL. Locked against tool overrides in production. | |
| SECURE_SCHEMA_ENV | No | Set to 'production' or 'prod' for strict startup validation. | development |
| FASTMCP_CHECK_FOR_UPDATES | No | Set to 'off' for predictable stdio startup. | |
| FASTMCP_SHOW_SERVER_BANNER | No | Set to 'false' to suppress the startup banner. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | Lists all user tables and views available in the current database. Use this to understand what architectural entities exist. |
| schema_overviewA | Summarizes available tables, views, primary keys, and foreign key relationships. Strictly constrained to structural metadata. Does not reveal data rows. |
| inspect_tableA | Exposes exact column names, types, nullability, primary keys, and foreign key relationships. Strictly constrained to structural layouts. Does not reveal data rows. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
list_tables and schema_overview both list tables/views, creating overlap. inspect_table is distinct but also covers PK/FK info that schema_overview summarizes. Descriptions help distinguish, but ambiguity remains.
Two tools use verb_noun pattern (inspect_table, list_tables), while schema_overview uses noun_noun. The inconsistency is minor but noticeable.
Three tools is appropriate for a focused schema exploration server. The count covers essential operations without being excessive.
Covers listing tables, detailed table inspection, and schema summary. Minor gaps like lack of view-specific inspection or filtering, but overall the surface is sufficient for the domain.