Skip to main content
Glama
adepanges

TeamRetro MCP Server

by adepanges

Related Servers

Alternatives to TeamRetro MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Jira Server/Data Center that enables issue retrieval, JQL search, comment posting, and Tempo worklog queries via the atlassian-python-api.
      19
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Implements a secure MCP server with API Key and JWT authentication, providing tools like echo, login, secure_action, and admin_action. Includes MCP Inspector integration for testing and debugging.
      1
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Jira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.
      531 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive, production-ready MCP server for seamless Jira Cloud integration, enabling AI agents and custom applications to manage boards, issues, users, projects, and workflows via natural language commands.
      383 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that wraps the Jira REST API v3, enabling issue management, searching, commenting, and transitions for openmrs.atlassian.net via Basic Auth.
      1
      -
    • A
      license
      C
      quality
      B
      maintenance
      MCP server for integrating with Bitbucket Cloud and Server APIs, enabling AI assistants to interact with repositories, pull requests, pipelines, and more.
      59
      28 npm
      3
      MIT

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, add_user vs. update_user are differentiated by create/update semantics, and list_team_members is distinct from list_teams in scope. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, such as create_team, update_user, and list_teams. This predictability aids agent understanding and tool selection, with no deviations in naming conventions across the set.

    Tool Count5/5

    With 11 tools, the count is well-scoped for managing teams and users in a TeamRetro domain. Each tool earns its place by covering essential operations like CRUD for both resources, plus specific actions like listing members, without being excessive or sparse.

    Completeness5/5

    The tool set provides complete CRUD and lifecycle coverage for teams and users, including create, read, update, delete, and list operations. There are no obvious gaps, such as missing pagination or filtering, and agents can handle typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive