tibero-mcp
Related Servers
Alternatives to tibero-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables safe schema exploration and read-only SQL querying of Tibero databases, with policy-enforced SELECT queries and table metadata inspection.6 npmMIT
- AlicenseBqualityCmaintenanceEnables LLMs to safely inspect CUBRID database schemas and execute read-only queries, with opt-in support for single-statement writes.11MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to database schema information generated by tbls and enables secure SQL query execution on MySQL and SQLite databases. Allows users to explore database structures, table relationships, and execute SELECT queries through natural language interactions.ISC
- AlicenseAqualityCmaintenanceEnables AI assistants to safely explore and query MySQL, MariaDB, PostgreSQL, SQLite and StarRocks databases through read-only tools for schema listing, table description, schema search, row sampling, query execution, and plan explanation. Enforces least-privilege accounts, engine-level read-only sessions with timeouts, parsed SQL guardrails, and column masking so runaway or unsafe queries are refused.8MIT
- AlicenseAqualityDmaintenanceEnables AI tools to interact with Oracle databases through query execution, schema browsing, stored procedure calls, and transaction management. Supports multiple database connections with safety features like read-only mode and dangerous query detection.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with relational databases such as MySQL, PostgreSQL, SQLite, SQL Server, and Oracle. Provides tools for querying, data inspection, and schema analysis with optional read-only mode.13 npm1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct step in database exploration: schema listing, table listing, table description, column search, querying, and plan explanation. The only near-overlap (describe_table vs search_columns) is clearly separated by scope: one table's structure versus schema-wide column lookup.
Four tools follow a clean verb_noun pattern (list_schemas, list_tables, describe_table, search_columns), but query and explain are bare verbs without a noun. The deviation is minor and the names remain unambiguous.
Six tools is well-scoped for a read-only database exploration server, with no redundant or filler tools. Each tool maps to a clear workflow stage from discovery to query execution.
The surface covers a full discovery-to-execution lifecycle: schemas, tables, columns, search, query, and explain plan. Minor gaps exist, such as standalone index/constraint exploration or procedure/function listing, but agents can work around these via describe_table and query.