Skip to main content
Glama
Sign In
CoraDB MCP Server

CoraDB MCP Server

Official
by apsisware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CoraDB MCP Server

No user-submitted related servers found.

    Related Servers

    • Demo Database MCP

      PhoenixCo-Founder
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables database querying and modification through an MCP server where each action is gated by human-granted scopes, per-call confirmations for destructive operations, and revocable access.
      MIT

    • Safe SQL MCP

      korolserhii
      A
      license
      A
      quality
      B
      maintenance
      Enables an MCP client to answer business questions by running read-only, allow-listed, masked SQL queries against a served database copy, with row/time limits and an audit log.
      3
      MIT

    • 多数据库 MCP Server

      CGAdmin544
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to securely query databases, list tables, inspect table schemas, and test connections across Oracle, SQL Server, MySQL, PostgreSQL, and SQLite using read-only SQL tools.
      4
      MIT

    • Read-only SQL

      lerenn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to run SELECT-only queries and inspect table metadata against configured databases via MCP Proxy, with timeouts, row and byte caps, and audit logging.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct activity: connection verification, schema introspection, read-only querying, mutating/DDL execution, and plan inspection. The only potential overlap is that execute_sql can also run SELECTs, but its description explicitly frames it as the transactional read-write path while execute_select is the guarded read-only path. Boundaries are clear enough that misselection is unlikely.

    Naming Consistency4/5

    Four tools follow a clean verb_noun snake_case pattern (describe_schema, execute_select, execute_sql, explain_query). connection_info breaks the pattern as a noun phrase, a minor deviation but still unambiguous and readable.

    Tool Count5/5

    Five tools is a tight, well-scoped surface for a database MCP: connect, inspect, read, write, explain. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The lifecycle is well covered: reachability check, live catalog introspection, read queries, transactional writes/DDL with dry-run, and plan explanation. Minor gaps exist around multi-database enumeration/switching and any explicit result-pagination or cancellation path, but agents can work around these.

    Resources