platypus-db
OfficialRelated Servers
Alternatives to platypus-db
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceZero-config MCP server that empowers AI agents to safely query SQL and NoSQL databases like PostgreSQL, MySQL, SQLite, MongoDB, and Redis.547 npm1MIT
- AlicenseNot gradedqualityBmaintenanceDesktop app with a local MCP server that lets AI agents query PostgreSQL, MySQL, SQLite and SQL Server read-only. Agents get the schema and, by default, counts and summaries instead of rows; columns you mark never send are refused in any form.2Apache 2.0
- AlicenseAqualityBmaintenanceOne config, one CLI that turns your databases (Postgres, MySQL, SQLite, MongoDB) into MCP servers for Claude, GPT, Cursor, and any MCP-compatible agent.31MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to securely interact with PostgreSQL databases with least-privilege scopes, PII masking, and human approval for writes.4MIT
- AlicenseNot gradedqualityDmaintenanceMCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB550Apache 2.0
- AlicenseNot gradedqualityAmaintenanceThe 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.480MIT
TDQS
Scored across 24 tools
Most tools target clearly distinct resources or actions, and the descriptions draw sharp boundaries between similar-sounding tools such as explain vs. estimate_change and run_query vs. sample_rows. A few pairs still require careful reading, but an agent can generally select correctly.
The set is overwhelmingly snake_case with a verb_noun pattern (list_objects, describe_table, propose_sql, search_history). Minor deviations like top_queries, next_page, server_activity, and explain are readable but break the pattern slightly.
At 24 tools, the surface is heavy for a database MCP server and sits at the upper end of the borderline range. Each tool appears purposeful, but the breadth of schema, query, admin, scripting, and proposal features makes the set large enough to feel burdensome.
The tool set covers connection discovery, schema and object introspection, querying, pagination, explain/estimate, profiling, sampling, cross-database queries, SQL and row-edit proposals, scripts, history, sessions, server activity, and schema comparison. No obvious lifecycle or workflow gap remains for the stated database-assistant purpose.