Skip to main content
Glama
YeomYuJun

Tibero MCP Server

by YeomYuJun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Tibero MCP Server

No user-submitted related servers found.

    Related Servers

    • TiDB MCP Server

      c4pt0r
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with TiDB serverless databases through the Model Context Protocol. Allows users to connect to and manage TiDB cloud databases using natural language through Claude Desktop.
      24
      Apache 2.0

    • SqlDb-MCP-Server

      PlanetMarc
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query SQL Server databases and retrieve schema information securely through the Model Context Protocol.
      2
      -

    • sqlserver

      AshwathDAzur
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query, analyze, and manage SQL Server databases through natural language via the Model Context Protocol.
      6
      1
      -

    • SQLServer MCP Server

      huang-develop
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to connect to SQL Server databases and execute arbitrary SQL operations, including queries, updates, table management, and script execution, through the Model Context Protocol.
      7
      -

    • MCP SQL Server

      ryudg
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI assistants with comprehensive access to SQL databases, enabling schema inspection, query execution, and database operations with enterprise-grade security.
      16 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: execute_sql handles arbitrary SQL queries, while get_table_info provides metadata about a specific table. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (execute_sql and get_table_info). The naming is predictable and readable throughout the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a database interaction domain. Core operations like listing tables, describing schemas, or managing connections are missing, making it under-scoped for typical database workflows.

    Completeness2/5

    The tool surface is severely incomplete for a Tibero database server. It lacks basic CRUD lifecycle coverage (e.g., no tools for listing databases/tables, creating/dropping tables, or managing transactions), which will cause significant agent failures in database tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources