safedb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | Database connection URL. Example: postgres://readonly:password@localhost:5432/app |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_schemasA | List database schemas allowed by the SafeDB policy. |
| list_tablesB | List allowed tables in an allowed schema. |
| describe_tableB | Describe columns for an allowed table and show configured masks. |
| run_readonly_queryA | Run a guarded read-only SELECT query against allowed tables. |
| explain_queryA | Run a guarded EXPLAIN SELECT query against allowed tables. |
| get_safedb_policyA | Return the effective SafeDB safety policy without secrets. |
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 6 tools
Each tool targets a distinct aspect of database safety: listing schemas/tables, describing columns, running queries, explaining queries, and retrieving policy. No overlapping purposes.
All tool names follow a consistent verb_noun pattern (describe_table, explain_query, get_safedb_policy, list_schemas, list_tables, run_readonly_query). No deviations.
Six tools cover the core functionality of a read-only safe database interface without being excessive or sparse. Each tool serves a clear and necessary role.
The tool set provides full lifecycle for read-only access: listing schemas/tables, describing structure, executing queries with EXPLAIN, and fetching policy. No obvious gaps for the stated purpose.