db-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTGRES_DSN | Yes | PostgreSQL connection string (e.g., postgresql://user:pass@host:5432/db) | |
| DB_BRIDGE_MAX_ROWS | No | Max rows returned per query | 1000 |
| DB_BRIDGE_ALLOW_DDL | No | Allow CREATE/ALTER/DROP statements | false |
| DB_BRIDGE_TRANSPORT | No | Transport mode: stdio, sse, or http | stdio |
| DB_BRIDGE_ALLOW_WRITE | No | Allow INSERT/UPDATE/DELETE | false |
| DB_BRIDGE_STATEMENT_TIMEOUT | No | Query timeout in ms | 30000 |
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 |
|---|---|
| queryA | Execute a parameterized SELECT query and return rows. |
| executeB | Execute a parameterized INSERT, UPDATE, or DELETE statement. |
| list_tablesB | List all tables in a schema. |
| describe_tableA | Describe a table's structure including columns, indexes, and constraints. |
| run_migrationA | Run a database migration (DDL statements) in a transaction. |
| explain_analyzeA | Get query execution plan with costs using EXPLAIN ANALYZE. |
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 has a clearly distinct role: query for SELECT, execute for DML, run_migration for DDL, explain_analyze for query plans, and list_tables/describe_table for schema inspection. There is no meaningful overlap that would confuse an agent selecting among them.
Most tools follow a clear verb_noun pattern, such as list_tables, describe_table, and run_migration. The bare verb tools query and execute break the pattern slightly, but they are standard database terms and remain predictable in context.
The 6-tool surface is well-scoped for a database bridge: it covers queries, changes, schema introspection, migration, and performance analysis without unnecessary duplication. Each tool serves a meaningful purpose.
The set covers the core lifecycle of database interaction: read, write, schema inspection, DDL changes, and query analysis. Minor gaps exist, such as no explicit transaction control for arbitrary DML batches or no tool for managing connections, but these are reasonable workarounds.