dbridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBRIDGE_DB_PATH | No | The database connection string (file path for SQLite, or URL for PostgreSQL/MySQL). Alternatively, provide as command-line argument. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | Lists every table in the connected database. Call this first to discover what data is available. |
| describe_tableA | Returns the columns of a table (name, type, nullability). Use it before writing a query. |
| sample_tableB | Returns the first rows of a table as a quick preview, to understand the data before querying. |
| count_rowsB | Returns the exact number of rows in a table. |
| run_queryA | Runs a single read-only SELECT or WITH statement and returns the rows as JSON. Writes are rejected and results are capped. |
| explain_queryA | Returns the query plan and estimated cost without running the query. Use it to check a query is cheap before running it. |
| get_limitsA | Returns the safety limits in effect (row cap, timeout, cost/rate limits, hidden and masked columns, table allow/block lists). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema | Every table with its columns, as one JSON document. |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: listing tables, describing schema, counting rows, sampling data, explaining queries, checking limits, and running queries. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_tables, describe_table, run_query). Verbs are descriptive and predictably used.
Seven tools are appropriate for a database bridge server, covering essential read-only operations like discovery, schema inspection, preview, counting, and safe query execution.
The tool set covers the full lifecycle of read-only database exploration: discover tables, describe schema, preview data, count rows, check limits, plan and execute queries. No obvious gaps for the stated purpose.