Skip to main content
Glama

Server Details

QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
85.0% over 52 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.8/5.0

Scored across 29 tools

Disambiguation5/5

Each tool targets a distinct resource and action, with overlapping tools like retro.actions.list and retro.board.actions.list explicitly differentiated in descriptions. The naming hierarchy (domain.resource.subresource.verb) helps keep properties separate.

Naming Consistency5/5

Tools follow a consistent dot-separated resource-verb pattern, with singular/plural usage following standard collection vs. single-resource conventions (e.g., games.list vs. game.get). All verbs are lowercase with underscores, making the surface predictable.

Tool Count2/5

With 29 tools spanning two distinct domains (poker planning and retrospectives), the surface feels heavy and may overwhelm users. The calibration suggests 25+ is excessive, and splitting into separate servers could improve focus.

Completeness3/5

The tool set covers most management tasks for both poker games and retrospectives, but lacks a core operation for adding messages/cards to a board, which is essential for a retro tool. Also, no board creation or deletion tools, leaving some lifecycle operations incomplete.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 29 tool updates
    • First observedpoker.game.get
    • First observedpoker.game.task.reveal
    • First observedpoker.game.task.select
    • First observedpoker.game.task.sync
    • First observedpoker.game.tasks.add
    • First observedpoker.game.tasks.import
    • First observedpoker.game.tasks.list
    • First observedpoker.games.create
    • First observedpoker.games.list
    • First observedpoker.iterations.list
    • First observedpoker.sources.list
    • First observedretro.actions.complete
    • First observedretro.actions.create
    • First observedretro.actions.list
    • First observedretro.actions.update
    • First observedretro.board.actions.list
    • First observedretro.board.health.get
    • First observedretro.board.insights.list
    • First observedretro.board.messages.delete_own
    • First observedretro.board.messages.list
    • First observedretro.board.messages.update
    • First observedretro.board.roti.get
    • First observedretro.board.suggested_actions.promote
    • First observedretro.board.suggested_actions.reject
    • First observedretro.board.summary.get
    • First observedretro.boards.list
    • First observedretro.boards.search
    • First observedretro.team.members.list
    • First observedretro.teams.list

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    F
    maintenance
    An unofficial MCP server that enables Claude to interact with TeamRetro.com's API for team retrospective management, providing direct pass-through to TeamRetro's public API endpoints with multiple authentication options.
    11
    32 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    A
    maintenance
    Keeps Jira Cloud, Jira Server, Linear or its own built-in tracker (plus Confluence pages) in one local SQLite file. Its MCP tools answer from that file: read-only SQL, full-text search across issues, comments and wiki pages, issue detail, sprint and retro reads.
    43
    Apache 2.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources