Skip to main content
Glama
sledmonkey

FlightPlan

by sledmonkey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to FlightPlan

No user-submitted related servers found.

    Related Servers

    • agenthelm

      jayasukuv11-beep
      A
      license
      A
      quality
      B
      maintenance
      Shared, versioned memory and governance control plane for AI coding agents. Compiler pipeline resolves architectural decision conflicts across Claude Code, Cursor, and custom agent fleets.
      3
      6
      MIT
    • asynkor by asynkor

      asynkorofficial

      asynkor
      A
      license
      Not graded
      quality
      D
      maintenance
      Coordination layer for AI coding agents working on the same codebase. Adds file locks, shared project memory, and cross-machine file sync so Claude Code, Cursor, Windsurf, and other MCP agents stop overwriting each other.
      50
      Apache 2.0

    • befall

      esenbora
      A
      license
      Not graded
      quality
      B
      maintenance
      Multiplayer coordination for AI coding agents: Claude Code, Codex CLI and Cursor share one room per repository. An agent claims a path glob before it edits and a conflicting claim is refused at claim time, so collisions are prevented rather than resolved at merge. Metadata only — source code and diffs never leave the machine.
      MIT

    • hivemind

      Leonhest
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables teams of coding agents to share one live plan synced through their existing git remote, so each agent receives teammates' contract, decision, and task changes at its next tool call. Provides tools for publishing contracts, logging decisions, adding and claiming tasks, and reviewing the plan for contradictions.
      99 npm
      3
      MIT

    • knos

      drexthealpha
      A
      license
      A
      quality
      A
      maintenance
      One local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.
      3
      5,161 PyPI
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool maps to a distinct lifecycle action (post, update, complete, mark_landed, get, list), so the boundaries are largely clear. However, list_intents bundles three distinct modes into one tool and its pre-planning collision check overlaps conceptually with the overlap-checking that post_intent and update_intent perform, which invites misselection.

    Naming Consistency5/5

    All six tools use a consistent snake_case verb_noun pattern built around the 'intent' resource (list_intents, get_intent, complete_intent, post_intent, update_intent, mark_intent_landed). The style is predictable throughout with only a trivial two-noun extension on mark_intent_landed.

    Tool Count5/5

    Six tools map neatly onto a coordination registry's minimal surface: register, update/heartbeat, complete, mark-landed, read one, and query many. No tool feels redundant and nothing is bloated.

    Completeness4/5

    The intent lifecycle is well covered: create (post), read (get/list), modify (update), and close (complete), plus the git-landing correction (mark_intent_landed). The only minor gap is an explicit retract/delete for an intent posted in error, though complete_intent's abandoned path partially covers this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources