dbridge-mcp
Related Servers
Alternatives to dbridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceRead-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.419 npm1ISC
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides safe, read-only SQL access for AI agents to query databases (PostgreSQL, MySQL, SQLite) with schema awareness and guardrails.21 npmMIT
- AlicenseAqualityCmaintenanceRead-only MySQL MCP server that lets AI agents list tables, describe schemas, and run SELECT/SHOW/EXPLAIN queries with a row cap, bound to a single database for safety.3MIT
- FlicenseNot gradedqualityFmaintenanceA read-only MCP server that enables AI agents to explore database schemas and execute safe queries on PostgreSQL and MySQL.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives an AI agent scoped, safe access to your Postgres databases with per-connection access control, row caps, timeouts, and defense-in-depth read-only enforcement.-
- FlicenseAqualityCmaintenanceA small MCP server that lets an LLM query PostgreSQL, MySQL, MariaDB, SQL Server, or SQLite databases safely — read-only, role-restricted, and with sensitive data blacked out.4-
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.