Skip to main content
Glama
zhouweico

mcp-yearning

by zhouweico

Related Servers

Alternatives to mcp-yearning

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Yearning SQL review platform, enabling read-only queries, ticket management (submit, audit, undo, rollback), query applications, comments, and data source/table exploration via REST/WebSocket APIs.
      19
      8 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for MySQL database integration with AI agents, enabling database exploration, CRUD operations, schema management, and performance monitoring through natural language.
      744 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A MySQL MCP server for secure database interaction, enabling schema inspection, query execution, and RBAC via AI coding assistants.
      1,352 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server for MySQL databases enabling AI assistants to interact with MySQL through secure, validated, and audited tools.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to MySQL databases for schema exploration, data querying, and SQL execution via natural language.
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query company logs, databases, caches, and config centers (e.g., Aliyun SLS, MySQL, Redis, Nacos) through local MCP servers, with read-only enforcement and SSH tunneling for production access.
      -

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: user info, source listing, database/table/field metadata, SQL check, order retrieval (my orders, audit orders), order details (detail, timeline, rollback, comments), and query execution. The two order-listing tools (my_orders vs audit_orders) are clearly differentiated by user vs auditor perspective.

    Naming Consistency4/5

    All tools share the 'yearning_' prefix and use snake_case. Most follow a verb_noun pattern (list_sources, list_tables, run_query) while some are noun-based (table_fields, order_detail). This is a minor deviation but overall predictable and readable.

    Tool Count5/5

    14 tools is well within the typical range for a domain-specific server. The count matches the platform's complexity and each tool covers a distinct aspect of the SQL audit and query workflow.

    Completeness2/5

    The tools heavily favor read/query operations but lack critical actions. The description in yearning_sql_check references a 'submit_order' tool that is absent, so the core workflow of submitting SQL for approval is incomplete. Additionally, there is no tool for approving/rejecting orders from the auditor perspective, only listing them. This leaves significant functional gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues