MongrelDB-Viewer
Related Servers
Alternatives to MongrelDB-Viewer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceFull featured MCP Server for MongoDB database analysis.105 npm208MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server for MongoDB 3.6+ providing read, write, metadata, and management tools.28 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for MongoDB with built-in safety features. Enables listing databases/collections, querying (find, count, aggregate), and writing (insert, update, delete) while preventing destructive operations like dropping databases/collections and bulk deletes without confirmation.27 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for comprehensive MongoDB integration, enabling database operations, document management, schema analysis, and query tools.21 npmMIT
- MIT
- AlicenseAqualityAmaintenanceMCP Server for local knowledge management. Semantic + keywords + tags846 PyPI24MIT
TDQS
Scored across 9 tools
Most tools are distinct, but schema-inspection duties overlap: list_tables vs database_overview both report tables, and describe_table vs constellation both expose columns and indexes. Descriptions hint at differences (connection-level vs graph-level), yet an agent can plausibly pick the wrong one for a simple 'what tables exist' or 'what indexes are here' question. Execution-oriented tools (execute_sql, semantic_search, install_dense_ann, reindex) are clearly separated.
Eight of nine names are snake_case, but the verb_noun pattern is broken by noun-only entries (constellation, reindex) and a noun_noun entry (database_overview). Naming is still readable and predictable enough to infer intent, but it is not a uniform convention.
Nine tools is well within the ideal 3-15 range and each maps to a real operation in a database viewer (inspect, query, index, maintain, discover providers). No tool feels redundant enough to remove wholesale, and none of the surface is padded.
Exploration, ANN setup, maintenance, and provider discovery are all covered, with execute_sql acting as a general escape hatch for anything missing. Minor gaps remain: no way to drop/uninstall an ANN index schema-side, no explain/query-plan tool, and no explicit listing of installed ANN indexes per column beyond describe_table.