Skip to main content
Glama
Sign In
Waypoint

Waypoint

by STiFLeR7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Waypoint

No user-submitted related servers found.

    Related Servers

    • DevLog

      ericd21
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to maintain a local engineering journal, log work manually or from git history, and let AI assistants query, summarize, and draft standup updates, changelogs, and retro notes.
      MIT

    • cemainou

      rtdesignstudio
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted work log your team's AI agents write: daily updates drafted from git and the session, tasks, time measured from agent sessions, project context and client access. 39 tools over Streamable HTTP, with personal keys for coding agents and OAuth for the Claude and ChatGPT apps.
      37
      Functional Source , Version 1.1, ALv2 Future

    • logbook-mcp

      cocaxcode
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to maintain a persistent developer logbook with notes, TODOs, reminders, code TODO scanning, and full-text search, while keeping all data local and optionally syncing with Obsidian.
      64 npm
      1
      MIT

    • meridian

      meridianmcp
      F
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory and task coordination for AI coding agents. Tracks sprint items, logs tasks, manages session handoffs, and surfaces HITL requests so you stay in control across single or parallel Claude Code, Codex, Cursor, and Windsurf sessions.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    The two read tools are the closest pair: take_fix returns a whole-portfolio snapshot while read_chart drills into a single voyage, and the descriptions make that scope split explicit. log_watch (the only write), status (install diagnostics), and eod_report (email builder) are each clearly distinct. The only friction is that the nautical metaphors ('fix', 'chart', 'watch') do not self-describe, so an agent must read descriptions rather than rely on names.

    Naming Consistency3/5

    All names are snake_case and drawn from a coherent nautical vocabulary, which is a plus. However the verb conventions are mixed: take_fix / read_chart / log_watch are verb_noun, while status is a bare noun and eod_report is an abbreviation-plus-noun with no verb. Readable, but not a predictable pattern.

    Tool Count4/5

    Five tools map cleanly onto five jobs: portfolio view, single-project view, log a watch, install health, end-of-day email. Nothing is redundant and nothing feels gratuitous, though it sits at the thin end of the 3-15 band.

    Completeness3/5

    Read, log, and report paths are covered, and log_watch can write Done/Next, but there is no way to create a new tracked project, change Status/Attention, edit or delete a log entry, or search across logs. Several of these gaps look intentional (files are the source of truth, log_watch is append-only), yet agents will hit dead ends on any lifecycle operation beyond appending a watch.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources