Skip to main content
Glama
claude-interview-mode

claude-interview-mode

by teabagkim

Related Servers

Alternatives to claude-interview-mode

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Lets Claude Code conduct long, structured interviews via a keyboard-driven local web form, with unlimited questions and options, recommendations, ranking, previews, and live follow-up questions.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives Claude Code a persistent identity and cross-session memory with semantic search over saved facts, decisions, and journals. It also detects and classifies user corrections into behavioral patterns with lifecycle trends, reflecting periodically to promote or retire working frameworks.
      6 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex CLI for an interactive plan-execute-review workflow, enabling Claude to interview, design, and review while Codex implements code changes.
      7
      50 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides Claude Code with cross-session memory, semantic recall of facts and decisions, and tracking of user corrections as behavioral patterns. Enables persistent identity, self-evaluation, and framework evolution so the assistant learns from past sessions.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives Claude Code persistent cross-session memory with semantic search, automatic detection and classification of user corrections into behavioral patterns, and self-evolving frameworks that refine judgment over time. Everything runs locally through hooks and MCP tools, with no cloud, API keys, or telemetry.
      6 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: start_interview initiates, record logs exchanges, get_context retrieves current state, end_interview concludes. No overlap or ambiguity.

    Naming Consistency4/5

    All tools use imperative verbs, mostly in verb_noun form (start_interview, end_interview, get_context). 'record' is a single verb but fits the pattern; minor inconsistency but still predictable.

    Tool Count5/5

    Four tools is ideal for an interview mode server. Each tool serves a fundamental operation (start, record, read context, end) without being overly minimal or excessive.

    Completeness4/5

    The tool set covers the full interview lifecycle (start, record, review context, end). A potential gap might be editing or removing a record, but the core workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues