lobsterdb
OfficialRelated Servers
Alternatives to lobsterdb
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables secure, direct access to PostgreSQL databases for queries, modifications, and schema exploration.-
- AlicenseNot gradedqualityCmaintenanceProvides AI-driven PostgreSQL database management with secure OAuth 2.1 authentication, enabling users to administer, monitor, and query databases with support for extensions like pgvector, PostGIS, and pg_cron.152 npm-
- AlicenseNot gradedqualityAmaintenanceEnables secure, AI-driven PostgreSQL database administration, observability, and querying with support for extensions like PostGIS and pgvector, connection pooling, and advanced tool filtering.145 npm12MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with PostgreSQL databases through natural language, with schema-aware query generation and enterprise safety controls.18161 npm2MIT
- FlicenseNot gradedqualityDmaintenanceProvides tools for managing PostgreSQL databases through the Managed DB API, including project creation, table management, migrations, backups, and more.-
- FlicenseNot gradedqualityDmaintenanceEnables querying and inspecting a PostgreSQL database, including executing SQL queries, listing schemas and tables, and describing table columns.-
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action: database lifecycle, SQL querying, schema introspection, migrations, snapshots, and account details. The query-vs-migrate boundary is explicitly clarified, and no two tools appear to do the same thing.
Most tools follow a clear verb_noun pattern (create_database, get_database, list_databases, introspect_schema, list_migrations). Minor deviations are snapshot (bare noun) and query/migrate (verbs without an explicit object).
Ten tools is well-scoped for a database provisioning and management server. Each tool earns its place, covering account, database CRUD, querying, schema introspection, migrations, and snapshots without excessive redundancy.
Core database and query workflows are covered, but database CRUD lacks an update/rename operation and snapshots can only be created, not listed, restored, or deleted. Migrations can be applied and listed but not rolled back or dropped, leaving some notable lifecycle dead ends.