Skip to main content
Glama
WorldStoryCm

Team Time MCP

by WorldStoryCm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Team Time MCP

No user-submitted related servers found.

    Related Servers

    • Agent Harness Kit (AHK)

      DmitryWatanabe34
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows by claiming tasks, logging actions, managing handoffs, and enforcing server-side health gates across explorer, consultant, builder, and reviewer roles. Specifications stay as Markdown on disk while tracked task state, acceptance evidence, and completion checks are owned by the server.
      29 npm
      MIT

    • ai-coordinator-mcp

      MaxxArtes
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a shared task state for local coding agents, letting them bootstrap a project, list and create tasks, resume work, write checkpoints, inspect configured routes, and plan worker runs. It also exposes a bounded delegation call that invokes configured local agent clients, returning a proposal that requires human review since it may consume quota or balance.
      PolyForm Noncommercial 1.0.0

    • Agent Harness Kit

      JanChevalier385
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to coordinate structured multi-agent workflows with documents, tracked tasks, handoffs, and health evidence. It owns task claims, action logs, and final health results while leaving specification files on the filesystem.
      29 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.3/5.0

    Scored across 27 tools

    Disambiguation3/5

    The task lifecycle tools are mostly distinct, but the large agent-coordination cluster has several easily confused pairs: ask_agent vs leave_agent_message vs reply_agent_message, get_task_agents vs get_agent_message, and ack vs reply vs wait. Descriptions clarify boundaries, but an agent must read carefully to avoid misselection.

    Naming Consistency4/5

    Most tools follow a consistent team_time_ + snake_case convention with predictable action/resource naming. A few entries are noun-style setup/configuration tools (context, bootstrap, workflow, agent_hooks_config) rather than verb_noun, but the overall pattern remains readable.

    Tool Count3/5

    At 27 tools this is heavy for a single MCP surface, though the server spans task management, workflow, pagination, command recovery, and multi-agent chat coordination. The count is defensible for the domain but still borderline: some coordination tools could likely be consolidated.

    Completeness4/5

    The surface covers the core lifecycle well: context/bootstrap, projects/members/tags, workflow, task list/get/create/claim/update/status/complete/release, plus command recovery and agent messaging. Minor gaps exist around destructive/admin operations such as project/member/tag mutation or task deletion, but core agent workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources