Skip to main content
Glama
clidey

whodb-cli

Official
by clidey

Related Servers

Alternatives to whodb-cli

Related Servers

  • A
    license
    A
    quality
    A
    maintenance
    One config, one CLI that turns your databases (Postgres, MySQL, SQLite, MongoDB) into MCP servers for Claude, GPT, Cursor, and any MCP-compatible agent.
    3
    1
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    MCP Chat is a CLI application that enables interactive chat with AI models via the Anthropic API, supporting document retrieval, command-based prompts, and extensible MCP tool integrations.
    2
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants like Claude to interact with MongoDB databases through standardized MCP tools. Supports full CRUD operations, aggregations, and natural language queries with Clean Architecture and dual transport modes (STDIO/HTTP).
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Multi-database management tool and MCP server supporting MySQL, PostgreSQL, SQLite, and Dameng DM8, enabling AI assistants to query and manage databases via stdio or HTTP.
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    A database MCP server providing 33 tools across PostgreSQL, MySQL, and SQLite, with connection groups, rollback, dump/restore, and schema auto-discovery via natural language.
    34
    42 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    The Multi DB MCP Server is a high-performance implementation of the Database Model Context Protocol designed to revolutionize how AI agents interact with databases. Currently supporting MySQL and PostgreSQL databases.
    468
    MIT

TDQS

B3.1/5.0

Scored across 156 tools

Disambiguation2/5

The surface is riddled with overlapping read tools that all answer 'what's in my project' (workspace_summary, workspace_map, project_health, project_resources, data_model_summary, resource_graph, next_actions, gap_analysis), and four competing write paths (generic create/update/action, typed source_create/create_dataset wrappers, preview, write_plan, workflow_apply). The near-identical preview_* family (preview_create_package, preview_import_package, preview_install_package, preview_shared_import, preview_shared_install) and the product-specific ontology query/rows/aggregate/stats/follow_link set are better delimited, but an agent must read long prose to choose correctly.

Naming Consistency3/5

Everything uses snake_case with the whodb_platform_ prefix, which helps, but there is no consistent verb_noun scheme: list tools are bare nouns (sources, datasets, ontologies, packages, teams), reads use inspect/read/view/get variably, and there are singular/plural pairs (app_sdk/app_sdks, app_view/app_views, project_access/resource_access, installation vs installations). The lone whodb_mcp_setup breaks the prefix convention entirely.

Tool Count1/5

156 tools is far beyond any reasonable scope and will swamp an agent's context and selection accuracy, even for a broad hosted data platform. Many entries are thin variations of each other, so the count reflects surface sprawl rather than earned capability.

Completeness4/5

Coverage is genuinely deep: CRUD for sources, datasets, ontologies, transforms, functions, apps and packages, plus sharing, lineage, versions, storage, org/team admin, confirmation lifecycle and workflow persistence. Some operations are only reachable through the catch-all whodb_platform_action and external schema document, which is a minor gap but not a dead end.

Maintenance

ActivityActive
ResponsivenessWithin a week