Skip to main content
Glama
danowicz

Ferry

by danowicz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Ferry

No user-submitted related servers found.

    Related Servers

    • CodeTour

      benstaniford
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to create animated, narrated tours of GitHub pull requests, with a local browser viewer showing diffs and code highlights while speaking the narration aloud.
      7
      MIT

    • MCP Walkthrough

      Stefan-Nitu
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to present interactive code walkthroughs with voice narration, opening files, highlighting code, and showing inline explanations with synchronized text-to-speech.
      5
      8 npm
      MIT
    • Flowcast by flowcast-studio

      Flowcastofficial

      flowcast-studio
      F
      license
      Not graded
      quality
      D
      maintenance
      Turn your AI coding agent into a producer of interactive, narrated walkthroughs — code, whiteboard, and 3D casts, each a single self-contained HTML file that opens in any browser. Runs locally over npx.
      1
      -

    • Freyja

      coadan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to scaffold, preview, inspect, navigate, capture, and build interactive HTML presentations authored as React/TSX source files. It operates the local presenter—keys, step tabs, URLs, and tools share one position—while agents edit the source directly.
      8 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action, from deck and slide CRUD to git inspection and viewer feedback. The only subtle overlap is between get_feedback and wait_for_feedback, but their descriptions clearly distinguish immediate retrieval from blocking wait, and resolve_feedback vs reply_feedback are similarly well separated.

    Naming Consistency4/5

    All operational tools follow a consistent snake_case verb_noun pattern (e.g., create_deck, add_slides, update_slide, wait_for_feedback). The lone deviation is authoring_guide, which is a noun phrase rather than an action, but the overall convention is predictable.

    Tool Count4/5

    18 tools is slightly above the ideal 3-15 range, but the server's domain is genuinely broad: deck lifecycle, slide editing, git diff import, viewer control, and feedback handling. Each tool earns its place, though a few could conceivably be consolidated.

    Completeness5/5

    The surface covers full CRUD for decks and slides, list/open/export operations, git change inspection and skeleton deck generation, plus a complete feedback loop (wait, get, resolve, reply). No obvious dead ends exist for the stated purpose of building and refining code-explanation decks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources