Skip to main content
Glama
nikp29

harness-homies

by nikp29

Related Servers

Alternatives to harness-homies

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables supervising and coordinating local coding agents across allowed repositories, including inspecting context, reviewing sessions, launching or continuing tasks, and retrieving redacted logs under owner-controlled access.
      14 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides a read-only interface to audit and continue coding agent sessions by extracting plans, intents, and edit authorship from history across multiple agents (Claude, Codex, OpenCode, Antigravity, Pi) via MCP, CLI, and Python SDK.
      18
      27 PyPI
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides a workspace-safe, read-only bridge between browser-based AI planning/review and local coding agents, enabling structured plan, execution summary, and review handoffs without granting shell, file write, or Git push access.
      11
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Kilo Code and Opencode conversation history stored in a local SQLite database, allowing users to list projects and sessions, read messages, and perform full-text keyword searches across all messages.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables browsing, searching, and importing sessions from multiple coding agents into the current one, or reopening them in their native agent, all locally and read-only.
      3
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct concern: listing all sessions, retrieving one session's metadata, fetching a transcript, and searching across sessions. The overlap between list_sessions and search_sessions is minimal and clearly differentiated by behavior.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_sessions, get_session, get_transcript, search_sessions. The naming is predictable and instantly readable.

    Tool Count5/5

    Four tools is well-scoped for a read-only session inspection server. Each tool covers a distinct aspect of the domain without redundancy or missing essentials.

    Completeness5/5

    For a read-only monitoring tool, the surface is complete: discover sessions, inspect one session, read its transcript, and search across sessions. No obvious lifecycle operations are expected here, so there are no meaningful gaps.