Skip to main content
Glama
ad19900913

Zentao MCP Server

by ad19900913
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Zentao MCP Server

No user-submitted related servers found.

    Related Servers

    • Glitchtip MCP Server

      CleverMobi
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Glitchtip error tracking platform through natural language. Provides access to issues, events, projects, teams, and organization management for comprehensive error monitoring and debugging.
      7
      15 npm
      3
      AGPL 3.0

    • Cursor MCP Server

      Buga-luga
      A
      license
      Not graded
      quality
      D
      maintenance
      Facilitates integration with the Cursor code editor by enabling real-time code indexing, analysis, and bi-directional communication with Claude, supporting concurrent sessions and automatic reconnection.
      4 npm
      39
      MIT

    • NocoDB MCP Server

      gordo-v1su4
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables direct integration with NocoDB databases from Cursor IDE, providing complete CRUD operations, search capabilities, and specialized tools for Discord workflow automation. Features production-ready deployment with Docker support and comprehensive monitoring.
      65 npm
      MIT

    • Azure DevOps MCP Server

      dhippley
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables interaction with Azure DevOps through Cursor chat, providing tools to manage builds, pipelines, work items, sprints, and board operations. Supports secure authentication via Personal Access Tokens and allows natural language-driven DevOps task management.
      1
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes: two for getting bug details (regular and market), two for listing assigned bugs (regular and market), and one for downloading images. However, rdms_get_bug and rdms_get_market_bug could potentially be confused as they both retrieve bug details, differentiated only by 'market' vs. regular, but their descriptions clarify this distinction.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with the prefix 'rdms_' and a clear verb_noun structure (e.g., 'download_image', 'get_bug', 'get_my_bugs'). This consistency makes the tool set predictable and easy to understand.

    Tool Count4/5

    With 5 tools, the count is reasonable for a bug tracking domain, covering key operations like retrieving bug details and lists. It's slightly lean but functional, as it includes core read operations and an image download utility, though it might benefit from additional tools for broader CRUD coverage.

    Completeness3/5

    The tool set focuses on read operations and image handling, with no tools for creating, updating, or deleting bugs, which are typical in bug tracking systems. This creates notable gaps in lifecycle coverage, though agents can still perform basic retrieval and analysis tasks with the provided tools.

    Resources